Made a map of Block Producers(organizations) locations

今天furnkil98发文整理了目前BP的分布状况。

完整地图链接

还附上了所有BP竞争者的信息列表

完整BP竞争者列表链接

此信息在EOSGO上的链接地址：https://forums.eosgo.io/discussion/558/made-a-map-of-block-producers-organizations-locations#latest

Basic Question Regarding B2B EOS Applications

乌克兰节点参与者RomanCryptoLions提出问题，以下是Mike针对每部分的回复。

Is it possible to be an open source business application on EOS and still cover your costs and reward Entrepreneurial risk?

In cryptoland, the way to cover your costs and reward your Entrepreneurial risk, it seems, is to issue your own token and use it as an access token to your application. The access token creates scarcity upon which you can build the economics of your business.

Answer: I would say that the token is a representation of value in a system, simple scarcity is not enough

If your code is opensource, there is a risk that some developer can simply remove the requirement for an access token and re-launch it as a completely free application with no scarcity. That's great for users, except there's no mechanism for rewarding entrepreneurs.

Answer: It would mean having to maintain a fork which is not straightforward in itself. In addition to this, you have removed all motivation from the system to make it better and support it. There is a lot more to a business than just the code.

For applications that rely on communities, the risk of re-launching the application as a free version is mitigated by the network effect. The application isn't valuable without a community around it.

All the big examples of block-chain based applications do indeed rely on communities: SteemIt, Bitshares, Everpedia.

But with B2B applications, the value is the application itself. Their value doesn't rely on the existence of a community. So what's an entrepreneur to do?

Answer: I think that most successful dapps will have to build a community around them who are prepared to contribute to it's success. If you are thinking about an enterprise app then the community may be both your customers but also independent contractors who are working on the software and improving it and providing consulting services.

Anyone interested in the success of the project vision should be fairly rewarded based on their risk. In the early days of a DAC the launch team are rewarded the most because they contribute the most value, but they cannot expect to keep receiving extra reward if they do not contribute.

Unless I'm missing something obvious, which is quite possible, the solution is to make important parts of the application not open source, thus ensuring that no one can remove your application's scarcity, and re-release it as freeware.

Is this right? Comments welcome.

上面这部分暂时没有回复。

原页面链接：https://forums.eosgo.io/discussion/519/basic-question-regarding-b2b-eos-applications#latest