مفهوم ماسترنود

أصبحت ماسترنود ، التي كانت فريدة من نوعها إلى شبكة داش ، شائعة الآن حيث تم تشبيك التكنولوجيا في بلوكشين أخرى. يصف هذا القسم من الوثائق مبادئ وآليات ماسترنود والخدمات التي يقدمونها لشبكة داش على وجه التحديد.

Simply put, a masternode is a server with a full copy of the Dash blockchain, which guarantees a certain minimum level of performance and functionality to perform certain tasks related to block validation, as well as PrivateSend and InstantSend, as the privacy and instant transaction features in Dash are called. The masternodes are paid for this service, using a concept known as Proof of Service. This is in addition to the Proof of Work done by miners to secure the blockchain. Masternodes are also allowed to vote on governance and funding proposals, with each masternode receiving one vote (yes/no/abstain) on each proposal submitted to the system.

يمكن لأي شخص تشغيل ماسترنود. الهدف هو الحصول على ما يكفي من اللامركزية لضمان عدم وجود شخص واحد يسيطر على جزء كبير من ماسترنود. ومع ذلك ، لتجنب انتفاخ الشبكة مع ماسترنود لا لزوم لها أو تشجيع المشغلين المتهورة ، هناك شرط واحد يجب الوفاء به: دليل على ملكية 1000 داش. لا يلزم أن تكون القطع النقدية في العمود الفقري ، ولكن يجب إبقاؤها بطريقة معينة تتسم بالشفافية على الشبكة بالكامل. إذا قام المالك بنقل أو إنفاق تلك القطع النقدية ، فإن ماسترنود يتوقف عن العمل ويتوقف الدفع.

Masternodes are paid by the network for the PrivateSend, InstantSend and governance services they provide. 45% of the block reward is paid out to the masternodes, 45% to miners and 10% to the budget. In practice, half of the reward from a normal block goes to the miner and half to the masternode. Then, every 16,616 blocks (approximately 30.29 days), a superblock is created that contains the entire 10% payout to the budget proposal winners. Masternodes are selected for payment in each block (approximately every 2.6 minutes) from a deterministic masternode list, and moved to the back of the list after payment. As more masternodes are created, the duration between payments increases. If the collateral behind a masternode is spent, or if a masternode stops providing services to the network for more than one hour, it is removed from the list until normal service resumes. In this way, masternodes are given incentive to provide efficient and reliable services to the network.

وجود العديد من الخوادم التي تحمل نسخة كاملة من بلوكشين والعمل للعملة يمكن أن يكون مفيدا للغاية. بفضل نظام المكافآت ، لا يوجد خطر من عدم وجود ما يكفي من ماسترنود ، ويمكن للمطورين الاعتماد عليها بسرعة نشر أي ميزة لامركزية جديدة يريدون تنفيذها. وهنا تكمن القوة الحقيقية لـ داش - وهو نظام محفز للآلاف من الخوادم الموزعة التي تعمل على مدار 24 ساعة طوال 7 أيام الأسبوع ، وهو ما يعني أن داش يمكن أن تتوسع بشكل أكثر كفاءة وتنشر الخدمات بسرعة أكبر من مجموعة من المتطوعين غير المتطوعين. لمزيد من ماسترنود ، أفضل وأكثر أمنا شبكة داش.

As of November 2018, the Dash network has over 5000 masternodes located in over 45 countries and hosted on over 140 ISPs. The block reward is approximately 3.34 Dash, so the selected masternode receives 1.67 Dash per payment or approximately 6 Dash per month. The block reward decreases by 7.14% approximately once per year, so the annual earnings for a masternode owner is approximately 7% of the collateral, and will decrease over time as calculated here. See this tool to calculate real-time payment rates, and this site for various real-time statistics on the masternode network.

DIP003 Masternode Changes

Dash 0.13.0 implements DIP003, which introduces several changes to how a Dash masternode is set up and operated. A list of available documentation appears below:

Important concepts and changes:

  • It is possible to upgrade an existing masternode in-place without starting a new server and without moving your 1000 DASH collateral.
  • A masternode was previously "started" using the masternode start-alias command based on a masternode.conf file. Under DIP003, this file is no longer used, and masternodes are "registered" instead of "started". Masternodes begin offering services when a ProRegTx special transaction containing a particular key is written to the blockchain.
  • As before in masternode.conf, the ProRegTx references the transaction id (txid) and index holding the collateral. The IP address and port of the masternode are also defined in this transaction.
  • The ProRegTx contains 2 Dash addresses (also called public keys) and one BLS public key, which represent 3 different roles in the masternode and define update and voting rights. The keys are:
    1. ownerKeyAddr: This is a Dash address (public key) controlled by the masternode owner. It is different from the address used for the collateral. Because the owner uses the private key associated with this address to issue ProUpRegTx transactions, it must be unique for each masternode.
    2. operatorPubKey: This is the BLS public key of the masternode operator. Only the operator is allowed to issue ProUpServTx transactions. Because the operator key is used during live masternode operation to sign masternode-related P2P messages, quorum-related messages and governance trigger votes, the BLS key must be unique for each masternode.
    3. votingKeyAddr: This is a Dash address (public key) used for proposal voting. Votes signed with the corresponding private key are valid while the masternode is in the registered set.
  • Masternode payments were previously sent to the address holding the collateral. Under DIP003, the owner should specify a different address to receive payments in the ProRegTx. The owner may optionally specify a non-zero percentage as payment to a separate masternode operator, if applicable.
  • The masternode configuration can later be updated using ProUpServTx, ProUpRegTx and ProUpRevTx transactions. See Updating Masternode Information in DIP003 and Updating Masternode Information in this documentation for more details.
  • All functions related to DIP003 will only take effect once Spork 15 is enabled on the network. Until then, it is necessary to set up the masternode following the old process and then work through the upgrade procedure. In this state, the masternode will continue to function in compatibility mode, and all DIP003 related functions, such as payments to a separate address or percentage payments to operators, will not yet have any effect. The ownerKeyAddr and votingKeyAddr must also be identical until Spork 15 is enabled.

The process of setting up or upgrading a masternode is as follows:

  1. Set up your server and operating system
  2. Install the Dash software and synchronize the blockchain
  3. Generate a BLS key pair and enter the private key on the masternode
  4. Prepare a ProRegTx transaction
  5. Sign the ProRegTx transaction
  6. Submit the signed ProRegTx transaction

Step 1 can be omitted if you have an existing server. Steps 2 and 3 require direct access to the masternode. Steps 3 and 4 require access to a Dash Wallet (or DMT). Step 5 requires access to the wallet actually holding the collateral. Step 6 requires a Dash balance to pay the transaction fee.

ماسترنود مقابل التعدين

ويستند داش ، مثل بيتكوين ومعظم العملات الرقمية الأخرى ، على دفتر أستاذ لامركزي لجميع المعاملات ، والمعروفة باسم بلوكشين. يتم تأمين هذا بلوكشين من خلال آلية توافق الآراء. في حالة كل من داش و بيتكوين ، فإن آلية التوافق هي دليل العمل (بو) ، التعدين محاولة حل المشاكل الصعبة مع أجهزة الكمبيوتر المتخصصة ، وعندما يحل المشكلة ، فإنهم يتلقون الحق في إضافة كتلة جديدة إلى بلوكشين. إذا وافق جميع الأشخاص الآخرين الذين يقومون بتشغيل البرنامج على أن المشكلة قد تم حلها بشكل صحيح ، يتم إضافة الكتلة إلى بلوكشين ويتم مكافأة عامل التعدين.

على أية حال ، تعمل داش بشكل مختلف قليلاً عن بيتكوين ، لأنها تمتلك شبكة ذات مستويين. الطبقة الثانية مدعومة من ماسترنود (العقد الكاملة) ، والتي تتيح الخصوصية المالية (الإرسال المخفي) ، والمعاملات الفورية (الإرسال الفوري) ، ونظام الحوكمة والميزانية اللامركزي. نظرًا لأن هذا المستوى الثاني مهم جدًا ، فإنه يتم أيضًا تكريم ماسترنود عندما يكتشف عمال المناجم كتلًا جديدة. الانهيار هو كما يلي: 45 ٪ من المكافأة تذهب إلى عامل التعدين ، و 45 ٪ تذهب إلى ماسترنود ، و 10 ٪ محجوزة لنظام الموازنة (التي أنشأتها superblocks كل شهر).

يشار إلى نظام ماسترنود بأنه إثبات الخدمة (PoSe) ، حيث أن ماسترنود توفر خدمات هامة للشبكة. في الواقع ، يتم الإشراف على الشبكة بأكملها من خلال ماسترنود ، والتي لديها القدرة على رفض الكتل المشكلة بشكل غير صحيح من عمال المناجم. إذا حاول أحد عمال المناجم أخذ المكافأة بأكملها لنفسه أو حاول تشغيل إصدار قديم من برنامج داش ، فإن شبكة ماسترنود ستعمل على عزل هذا الحظر ، ولن تتم إضافته إلى بلوكشين.

باختصار ، عمال التعدين السلطة الطبقة الأولى ، وهو الإرسال الأساسي واستلام الأموال ومنع مضاعفة الانقراض. ماسترنود السلطة في الطبقة الثانية ، والتي توفر الميزات المضافة التي تجعل داش مختلفة عن العملات الرقمية الأخرى. ماسترنود لا الألغام ، والتعدين أجهزة الكمبيوتر لا يمكن أن تكون بمثابة ماسترنود. بالإضافة إلى ذلك ، يتم تأمين كل ماسترنود بـ 1000 داش. هذه الداش تبقى تحت السيطرة الوحيدة لمالكها في جميع الأوقات ، ولا يزال يمكن إنفاقها بحرية. لا يتم تأمين الأموال بأي شكل من الأشكال. ومع ذلك ، إذا تم نقل الأموال أو إنفاقها ، فستتحول إلى ماسترنود المقترن دون اتصال وتتوقف عن تلقي المكافآت.

منطق الدفع

Masternode payments in Dash version 0.13.0 are entirely deterministic and based on a simple list sort algorithm. For documentation of version 0.12.0 payment logic, see the legacy masternode payment documentation. Dash version 0.13.0 implements DIP003 and defines two sets of masternodes.

  1. The full set, which contains all registered masternodes that have not spent their collateral funding transactions.
  2. The valid set, a subset of the full set which contains all masternodes which are not marked as Proof of Service (PoSe) banned.

Each masternode in the set of valid masternodes, identified by its registration transaction ID, is associated with the block at which it was last paid. If it has never received payment or was banned for failing to meet the PoSe requirements, then the block at which it was first registered or at which service was restored is used instead. The list is sorted in ascending order by this block height and ProRegTx hash (as a tie breaker in case two masternodes were registered in the same block), and the first entry is selected for payment.

Proof of Service

Proof of Service (PoSe) is a scoring system used to determine if a masternode is providing network services in good faith. A number of metrics are involved in the calculation, so it is not possible to game the system by causing masternodes to be PoSe banned for failing to respond to ping requests by e.g. a DDoS attack just prior to payment. Each failure to provide service results in an increase in the PoSe score relative to the maximum score, which is equal to the number of registered masternodes. If the score reaches the number of registered masternodes, a PoSe ban is enacted and the masternode must be repaired to ensure it provides reliable service and registered in the list again using a ProUpServTx. The current scoring rules as of Dash 0.14 are:

  • Failure to participate in DKG= 66% punishment
  • Each subsequent block reduces PoSe score by 1

اختيار النصاب

In past versions of Dash, quorums of 10 masternodes were formed spontaneously to lock InstantSend transactions. As of Dash 0.14, quorums are deterministically formed, contain more masternodes and remain alive for a longer period of time. While they remain responsible for InstantSend transactions, the locking mechanism has changed to automatically attempt locks on most network transactions according to the requirements described here. Masternodes are now also responsible for more network consensus functions, such as ChainLocks. Masternode quorums are formed through a process of distributed key generation. Failure to participate in DKG will eventually result in a PoSe ban as described above.

متطلبات ماسترنود

  • 1000 داش: يمكن القول الجزء الأصعب. يمكن الحصول على داش من التبادلات مثل Poloniex و Bittrex و Kraken و LiveCoin. خدمة Shapeshift هي أيضا وسيلة ممتازة.
  • A server or VPS running Linux: Most recent guides use Ubuntu 18.04 LTS. We recommend VPS services such as Vultr and DigitalOcean, although any decent provider will do. Generally an instance with low to average specifications will do, although performance requirements will increase according to this roadmap.
  • عنوان IP مخصص: تأتي هذه عادةً مع خادم / VPS .

In addition to the 1000 Dash held in collateral, masternodes also have minimum hardware requirements. For Dash versions 0.14 and higher, these requirements are as follows:

  الحد الأدنى موصى به
CPU 1x 1 GHz 1x 2 GHz
الذاكرة 2 GB + 2 GB swap 4 GB + 2 GB swap
القرص 40 GB 60 GB
الشبكة 400 GB/mth 1 TB/mth

يتراوح عرض النطاق الترددي ماسترنود بين 300-500 غيغابايت في الشهر ، وسوف تنمو كما تفعل الشبكة.

تورة داش

The exact hardware requirements for Dash Evolution masternodes have yet to be determined, although some pointers can be taken from the roadmap and this blog post. It should be possible to run Dash masternodes on normal VPS servers until the block size reaches approximately 20 MB, after which custom hardware such as GPUs and eventually ASICs may be required.