Enforcing the EOS Block Producer Agreement

UPDATE: All six accounts have reregistered with a website containing a valid bp.json file. While the websites are empty and the BP info is mostly bare, we believe they now meet the requirements of Section 6 of the Block Producer Agreement which is to provide functioning API and P2P endpoints to the public. For this reason, as we stated we would do, we have canceled the multisig proposals.

Thank you to everyone who supported this effort. We saw many block producers and community members quickly rally to help enforce the rules and test the process, and in the end the network was improved.

更新：之前被点名的六个帐户都已重新注册了包含有效bp.json网站。虽然网站是空的，而且几乎没有任何BP信息，但我们认为它们现在满足了“区块生产者协议”第6条的要求，该协议旨在向公众提供功能完善的API和P2P接入点。因此，我们已经取消了之前发布的多签提案。

感谢所有支持者! 我们看到许多区块生产者和社区成员迅速会集起来帮助执行规则和测试流程，最终使主网得到了改善。

Aloha, Friends!

中文版请见下方。

Back in July 2019 a new Block Producer Agreement was proposed by EOS42, with much input from the community, and in August it was approved and executed by the active block producers. This agreement is in the form of a Ricardian Contract on the EOS “regproducer” action, and in conjunction with the EOS User Agreement, states that any EOS account that registers as a block producer is bound to it. The full contract can be viewed here.

Today we want to bring attention to section 6 of the Block Producer Agreement, which states that block producers “will provide functioning and queryable public P2P and API endpoints”. It doesn’t specifically state how the endpoint information is to be shared, but the traditional way block producers do this is with the EOS BP Information Standard, which depends on including a website when calling “regproducer”.

Looking over the current list of paid active and standby block producers, we have some that have not provided a functioning website, and therefore to our knowledge, have not shared any API or P2P endpoint information with the public. Here are those accounts with details:

Ideally, we could contact them and ask about the situation, but without any website or contact info we have no way to do that. Therefore we are moving forward with section 13 of the contract and have issued multisig proposals to call “rmvproducer” on these accounts, which will remove them from the standby list if approved. If the accounts are updated to show website and API/P2P endpoints before the proposals are approved, we will cancel the proposals.

We ask that active block producers please review the information provided and consider approving the following proposals:

stargalaxybp: https://bloks.io/msig/alohaeosprod/rmvsbpone

eosrainbowbp: https://bloks.io/msig/alohaeosprod/rmvsbptwo

validatoreos: https://bloks.io/msig/alohaeosprod/rmvsbpthree

eosathenabp1: https://bloks.io/msig/alohaeosprod/rmvsbpfour

eosunioniobp: https://bloks.io/msig/alohaeosprod/rmvsbpfive

eoszeusiobp1: https://bloks.io/msig/alohaeosprod/rmvsbpsix

At Aloha EOS, we believe that enforcing the Block Producer Agreement will lead to a more resilient network, and we hope others agree.

Aloha EOS

Aloha，朋友们！

在 2019 年 7 月 EOS42 提出了新的《区块生产者协议》，当时得到了社区的大量建议，并在 8 月得到了超级节点的批准和执行。该协议以李嘉图合约的形式出现在 EOS 主网 EUA 的 regproducer 部分。这意味着任何注册为区块生产者（节点）的 EOS 帐户都必须遵守此协议。点击这里查看完整的李嘉图合约内容。

在这里，我们想请大家注意上述李嘉图合约的第 6 条，第 6 条指出，区块生产者“将提供功能齐全且可查询的公共 P2P 和 API 接入点”。这条要求除了指出节点有义务向开发者提供 API 接入点之外，更大的意义在于让 EOS 网络上各节点之间的连接更加紧密且顺畅，从而使得 EOS 网络更加安全和稳定。它没有具体说明如何共享这些接入点的信息，但是大部分节点都是通过在自己官方网站的根目录下放置 bp.json 文件来共享这类信息的。而官方网站的网址则可以在调用“ regproducer”注册节点时进行指定。

按照上述要求，我们遍历了当前所有的超级节点和备选节点（有每日奖励的节点），发现有一些节点尚未提供官方网站，也没有公开提供 P2P 和 API 接入点信息。以下是这些节点账户的详细信息：

一般情况下，社区会尝试与他们联系并询问情况，但是在没有任何网站或联系信息的情况下我们无能为力。因此，我们将执行上述李嘉图合约的第 13 条，通过多签提案的方式调用“ rmvproducer ”接口移除上述这些节点。如果这些多签提案得到批准，这些节点将在备选节点中被删除。如果这些节点在批准提案之前及时更新网站和 API 以及 P2P 接入点信息，我们将取消提案。

我们请求超级节点查看我们所提供的信息，并考虑批准以下提案：