0.11.1版本 立即支付升级说明

Alexy

Well-known Member
Foundation Member
Dash Support Group
Oct 29, 2014
134
203
193
v0.11.1 - InstantX Development Update

0.11.1版本 立即支付升级说明


Now that the network has updated to version 11 and is stable, I thought it might be a good idea to lay out what the next we have in store for the next release and future plans. We’ll be leveraging our larger development team and working on a few projects at once to enable to a few new exciting features at once.现在网络版本已经升级到了0.11并且很稳定,我想应该发布出下个版本的更新内容和未来的计划了。我们将会继续扩大开发小队人数,同时研发并完成几个令人兴奋的项目。


Enforcement
Network fragmentation has been corrected on the network and we’ve enabled enforcement. Those not paying the correct node after today will simply be rejected by the network.


强制升级

网络分叉已经被修改完成,我们已经强行升级了。那些还没有升级的节点今天过后会被网络拒绝。

InstantX
A couple months ago I open sourced the design so that I could work with researchers on perfecting it. However, it’s not presently done and the code is a simple prototype of what I intended. I would recommend other crypto-currencies from not using it until we’ve had a chance to thoroughly test and refine the logic, otherwise grave damage could be done to your network.

We’ll begin finishing development on instantX immediately and work on the stability of the system. This will be done over the next few weeks on testnet and will be a completely open public testing phase.

立即支付

几个月前我发布了立即支付的源代码,想和其他研发人员一起完成。但是现在还和刚开始一样,没有改进丝毫。我建议其他加密数字货币在我们完善它之前不要使用,否则会对网络造成巨大的损坏。我们会立刻开始对立即支付项目的研发,使它在系统中稳定。预期几个星期后在测试网络上完成,其后投入公测阶段。


Masternode Changes / Improvements
As an upgrade to the masternode system, we’re going to be moving to a token-based system, where you’ll only be required to gain access to your cold wallet every few months. When starting a masternode, one will simply execute the “masternode generate-token” command, which will sign the key and generate a tokenized string to put into the masternode.conf. Using this signature masternodes can be restarted multiple times, even with protocol version updates.

The pinging system (dseep) is going to be replaced with a “challege request” system, which will be done in a completely decentralized way. Other masternodes on the network will be elected each block to check on their peers by initiating a “challenge request”, if a masternode fails multiple of these in a row by failing to respond it will be removed from the list.

As be move forward into the future, static IPv4 IPs will continue to get more scarce. In the next release we will begin to allow non-static IPs to be used as long as the client is reachable and can answer challenge requests.

主节点的变化/改善随着主节点系统的升级,我们将会进入标记化系统,你只需被要求每几个月使用一次冷钱包。当开启主节点时,只需要通过执行“masternode generate-token”命令,会产生私钥和标记化的字符串,将它放入主节点配置文件。使用这个标记可多次重启主节点,甚至进行协议版本的升级。回音系统(暂定)将会被“任务挑战”系统取代,一切以分布式方式完成。其他主节点将会选取各个块,通过“任务挑战”方式与另外的主节点核实。如果该主节点多次连续没有做出正确回应,将会被移除。预计未来静态的IPv4 IP将会出现更多的问题。在下一个版本中,我们将开始允许非静态IP的使用,前提是用户可以完成“任务挑战”。

Beyond version 11.1 (will not be in the InstantX release)


Masternode Blinding
Recently a paper by 3 researches at Saarland University came out describing a new technique, while there are someserious problems with the approach they take, the concept of blinding the users they use is novel. In CoinShuffle, each output is sent to the next peer in a circle, one at a time. The new peer adds an output, shuffles and then sends the list again. We can do this and actually improve upon it.

To implement blinding, each user would connect to one completely random masternode and say "Send masternode X this output/value for mix N" and pass a single output. That output would be passed to the leading masternode. It would take access to all masternodes used to know who did what, which is as solid as M rounds mathematically (M = number of outputs). This is great because all users can submit all inputs at once. So it's super fast compared to CoinShuffle and even more secure.

11.1版本之后(不会出现在立即支付版本中的)


主节点提速

最近,萨尔兰大学的研究组提出了一项新技术的研究报告.虽然他们在研究中遇到了阻力,但他们如何加速洗牌的理念十分新颖。在洗币过程中,每个输出节点一次只能向下一个节点发送一次信息。这个新的节点接收后,洗牌,之后再向下一个节点发送,依此类推。我们也可以这样做,事实上还能在这基础上进行改进。

为实行加速,每个用户需要连接一个完全随机的主节点,这里称为“主节点X this output/value for mix N” and pass a single output. That output would be passed to the leading masternode. It would take access to all masternodes used to know who did what, which is as solid as M rounds mathematically (M = number of outputs)<<由于怕翻译有误,要核实下>>.这样做的好处在于所有用户可以同时提交输出申请,这样与之前的洗币方式相比快了很多,而且更加安全。


Decentralization of the masternode payment system

Currently, there is a node that signs a message for each block and says which masternode should be paid for that specific block. As many of our users know, the centralized reference node was a temporary solution to the problem of enforcing masternode payments. Miners use this when creating the block to ensure they comply, if a miner tries to cheat the system, the block will be rejected by the network. This is a great solution temporarily, but isn’t decentralized enough.

To explain the new completely decentralized strategy, first we have to explain exactly how masternodes work. When a masternode starts, it relays a message called the “masternode election entry”. This puts the masternode into a list on all clients on the network and allows them to be used by all of the clients on the network. Every few minutes, these masternodes ping the network saying they’re still alive and allowing them to earn interest payments.

To decentralize this system, we propose a new system we’ll call “Masternode mining”. This simply means that when miners receive a new “masternode election entry” and solve a block, they will append the masternode to the block. Each block can contain up to 10 masternode list changes. So by following the normal progression of the blockchain, you will be able to compile a list of all known masternodes. This system is also highly resistant to attack and the same list can be compiled by any client on the network.

For example:
Block 1: Add mn1, mn2, mn3
Block 2: Add mn4, mn5
Block 3: Remove mn2 //mn2 fell off the network


-- currently the masternode list contains mn1, mn3, mn4, mn5

Block 4: Add mn6, mn7
Block 5: Add mn2 //mn2 came back


-- example attack: --

Block 6: Remove mn1, mn2, mn3, mn4, mn5, mn6 //miner owns masternode 7, wants control of the network
Block 7: Add mn1, mn2, mn3, mn4, mn5, mn6

In this case a majority of mining power is required to control the masternode list. If a miner has enough computing power to alter the masternode list, they will also have enough power to double spend with a 51% attack. Therefore this is the safest solution to decentralizing the payment.


分散式主节点奖励系统现在,有一个特定的节点在每一个块中广播哪个主节点将会获得奖励。如大家所知,中心化参考节点只是执行主节点奖励的一个临时方案。我们用它来确保矿工遵守规则,如果有矿工想欺骗系统,那么由矿工所挖出的块将会被网络拒绝。这是一个非常好的临时解决方案,但在“去中心化”一点上还做的不够。为了解释全新的去中心化策略,首先我们要解释主节点的工作原理。当主节点运行后,它会转述一条被称作“主节点当选登记”的信息。这会将主节点列入在网上的所有用户的清单中,并允许所有用户使用它。每几分钟这些主节点就会向网络广播它们还在运作中,从而允许它们获得奖励。为了完成非中心化系统,我们计划做一个名为“主节点采矿”的新系统。简单来说,当矿工接收到了主节点的消息,并挖出一个新块时,会把主节点信息写入块中。每个块可以包含10个主节点清单。通过延续数据块链进程,矿工可以编入所有已知的主节点。这个系统也有着很强的防御能力,同一个主节点清单也可以被网上的任何用户编辑。
例如:

第一个块:添加1号,2号,3号主节点

第二个块:添加4号,5号主节点

第三个块:移除2号主节点//2号主节点掉线


--那么现在主节点列表上包括了1号,3号,4号,5号主节点

第四个块:添加6号,7号主节点

第五个块:添加2号主节点//2号主节点上线


--假设攻击:--


第六个块:移除1号,2号,3号,4号,5号,6号主节点//矿工持有7号主节点,想要控制网络

第七个块:添加1号,2号,3号,4号,5号,6号主节点


在这种情况下,想要修改主节点列表需要获得绝大多数的算力才可以。若他们有足够的算力去修改主节点列表,那么他们也可以占据51%的算力来攻击。因此这是达成去中心化奖励制度的最安全的方法。
 

Alexy

Well-known Member
Foundation Member
Dash Support Group
Oct 29, 2014
134
203
193
I’m little confused about the Masternode Blinding and Decentralization of the masternode payment system parts. Could you guys Naruto Raico check and approve it again? Thank you^^:D