I transferred the coin - successfully !
TxHash: 0xe1665457d9df6d6b0b61a51156be227e5c2af435b4c5c4df0a0a633368a3f249
but credited to my wallet denied! and that's what they wrote back
Entering coins will be available after updating the source code of the wallet. Unfortunately, developers do not hurry to send updates

• Therefore, in order to avoid losing users' funds, the network is not available.
  If you have updated coin sources, send it to us and we will promptly fix the problem on the coin.
  help me

Hello

My name is Michael Asumcinei and I would like to contribute with Italian translations.

I can do that only using Github as I am an adopter of Utopian.io project to reward open source software.

Just let me know if you are interested and I will be there for it

Best Regards
Michael Asumcinei
steemit.com/@Digitalplayer

I installed "Marddown Preview Plus" package in Atom and opened "TechnicalWhitePaper.md" in it. Texts were typeset well, but the pictures were not shown.

And I have try other editors, such as Sublime and Notepad++, the problem existed.

Why?

Hi!

Thank's for the quite detailed white paper. However, to me it is not yet clear how the token situation behaves. Are there different kind of tokens? One for application operators, one for node operators, one for block produces and voters? What is the incentive to operate an EOS computation node? Which token to use for voting? When voting for one of the 21 block produces, will I as a voter be receive a share of the earned tokens of block producers? Most likely you will finance EOS through investores buying your tokens, so what's the business case for these investors? Being one of the 20 most voted block producers or the single random token holder is very unlikely and if that is really necessary to receive RoI, I'd consider EoS to be a scam.

Maybe you could bring light into the situation and describe which tokens exist, what they are good for and what the advantages/disadvantages of them are in a more clear and detailed way. Because I really like the idea behind EoS and would like to support it - once I understand the business model =)

with best regards,
Miek

I'm working on app for whitepapers and wanted to include eos. Have you got whitepaper in html or md.
Regards,
PJ

This issue target Subjective Best Effort Scheduling part of the Whitepaper

How exactly will Block Producers implement their own rate-limiting Algorithm in practice? Will they have to come out with their own solution for that?

Since smart contracts will be deployed once and excecuted many times can each executed wasm instructions be indexed into different bandwidth class based on preliminary test on each smart contract to be deployed on the main blockchain? One example solution is by preprocessed any smartcontract to be deployed on the blockchain by running said smartcontract into a testnet to see its resource consumption which then can be assigned a resource-consumption classifier once deployed into the main blockchain.

So the EOSIO software only needs to compute N X M to get a max transactions allowed per each block. Where N= number of transaction, M=[resource classifier1, resource classifier 2,...], X is standard matrix operation. Larger than just to compute N number of transaction but negligible enough in performance hit on the blockchain speed in the grand scheme of things.

Just one bare example of course. Criticism, help in fleshing this idea will be welcomed.

Hopefully this will lead to less subjectivity on the hands of Block Producers, which subjectivity can lead to DOS/ Favouritism by BPs.

The picture used for Evaluating Permissions appears to be incorrect.
https://github.com/EOSIO/Documentation/blob/images/images/diagram2grayscale2.jpg

@ EXCHANGE.CONTRACT must be associated with FRIENDS for the description and illustration in the figure.

Where should I send my CV to work with you guys?

如果你是我们的老读者，应该知道我们一直很关注EOS，对EOS的创新精神不吝各种溢美之词。同时，导师自己也是身体力行的支持EOS，分三次在低点买入，成本大概30元左右，占全部数字货币资产的比例大约是20%。当然了，区块链条的同事们，据我了解，也都是手里或多或少拿着一些EOS。

上个周末，区块链条的同事们坐一起吃烧烤，同时进行头脑风暴。大家讨论的中心就是EOS。经过长达两个小时的讨论，我们达成了初步共识：EOS按照目前的状态走下去，必定要衰败

今天，我们从EOS-RAM这个小的切入点，来分析一下EOS所谓的“免费”，究竟是怎么一回事。

640.webp.jpg

截止2018年7月9日早09:50，EOS-RAM最新价格为0.3382EOS/KB，使用率为50.57GB。这个价格，比起7月3日写文：熊市暴涨4000%，EOS的ram到底是个啥？之时的最高点，已经腰斩往下了，但仍处于高位。在7月3日，导师极力告诫大家不要接盘，不听话的，罚你去教室后面站着去。

今天我们要重新系统的分析一下EOS-RAM。

我们需要讨论的问题如下：

EOS-RAM到底是什么？

EOS-RAM是怎么交易的？对手盘是谁？它的bancor算法究竟是怎么回事？

EOS-RAM的需求量如何？

EOS真的是“免费”的吗？

我们该如何看待？

第一个问题：EOS-RAM到底是什么？

这东西，在EOS之前从来都不是关注点。有智能合约的公链，比如ETH，相当于所有挖矿的显卡都是处理器，都是内存，相应的记账需要手续费（gas），你不能让矿工白忙活对吧。EOS里没有矿工，只有DPOS记账，所有节点轮番来，在这里，超级节点就是一个公共服务器。截一张图，大家看一下超级节点到底做了什么工作。

640.webp (1).jpg

这张图显示了每个节点生成了多少区块。仔细看右边的节点列表，耳熟能详的eos北京、eos蚂蚁矿池、eos火币矿池均在其列。

只是记账，那是远远不够的，不管是交易、注册用户、运行Dapp，都需要服务器提供内存。我们在之前的文章：熊市暴涨4000%，EOS的ram到底是个啥？里面已经提到过了，EOS的ram（内存）一共是64G，而正因为上限暂时是固定的，从而引起了人们的争抢。

第二个问题：EOS-RAM是怎么交易的？对手盘是谁？它的bancor算法究竟是怎么回事？

与一般吃瓜群众理解的不同，EOS-RAM并不是用户之间进行交易，而是用户与系统进行交易。

点解？

你可以这样理解：EOS的所有RAM，最开始都掌握在系统的手里。你如果想买，你就去找系统抵押（注意，严格意义上你并没有买到RAM，你是抵押了手里的EOS获得了RAM的使用权），那么系统就把你的EOS先锁在系统里，同时给你一部分的RAM使用权。（现在有些交易所开通了EOS兑换RAM的交易对，一定要小心，因为你的对手盘并不是别的用户，注意看清楚交易所是帮你买进RAM还是在交易所账户里空转）

接下来是重头戏，我们来说一下EOS-RAM独特的bancor算法。

还是要举例子来说明。我现在手里拿着一个篮子，这个篮子里有一些饼。有个人想吃饼，于是拿一块钱给我，我就给了他一个饼。第二个人来找我买饼，也掏出一块钱，我摇摇头说，刚才那个饼一块钱，我看那个人吃的挺开心的，所以我觉得我的饼应该比一块钱更值钱，你要拿两块钱才能买我的一个饼。于是那个人拿了两块钱买了饼，第三个想买饼的人，我找他要三块钱，以此类推。

这种买卖的实质，就是越往后面，饼越贵，总有一天这个饼谁也吃不起，于是再跟之前那样一块一块跌回来。

但是，EOS的bancor算法可不是卖饼这样温情脉脉的线性函数。我们来看一张表。

640.webp (2).jpg

一开始，饼还是一块一个往外卖，涨价也不是很明显。但是越往后，你会发现指数函数的增长剧烈程度已经远远超乎你的想象，RAM越来越少，争夺越来越激烈。最极端的情况，就是现有的64G全部卖完，那样的话，需要所有的10亿EOS全部填进来买单。有兴趣的可以自己算一算1KB是多少钱。

那么目前来看，0.3EOS/KB的价格似乎还处于一个很温柔的阶段？

别急，继续往下看。

第三个问题：EOS-RAM的需求量如何？

所有的物品，离开了需求谈价格，都是扯淡。

那么EOS-RAM的需求如何？我们以注册一个EOS用户为例来解答这个问题。

过去，不管是ETH还是BTC，我们从来都是随用随搞，下载个钱包，钱包直接就给你生成一个地址，简单方便。而EOS则不然。

不知道你们注意到没有，当你把EOS私钥输入到imtoken里，imtoken只会留10个EOS在你账上，剩下的需要72小时赎回，并且依然有0.5个EOS被抵押。（见文章：EOS主网上线，如何在Imtoken里导入EOS钱包？）聪明如你肯定已经猜到了，这0.5个EOS就是抵押给系统了，为的是获取一定的资源保证你的账号能运行。

在实际操作中，一个新的账号，需要大约4KB的内存（以今日价格计算，需要1.3个EOS左右，导入imtoken的那都是早期用户，RAM还比较便宜，所以才跑得起来），另外还需要少许的CPU和带宽抵押，你的这个账户，才能够正常的转账、运行。以目前EOS的价格（57元）来计算，需要大约80元的EOS，才能注册生成一个新的EOS账号。

区块链条有很多合作伙伴，不少都是有志于在EOS上搞一番大事的。在EOS亚洲下面有一个游戏组，不久前开发了一个游戏，导师去玩了一下，感觉很不错，内部测试的结果也很棒，各方面反响都很好，但是最近该项目熄火了，导师去问项目组负责人是怎么回事，负责人回答说：每一个新来的用户，项目组都需要在EOS上给他新注册一个地址，而这一个地址就要花几十甚至上百元（前几天EOS-RAM的价格飙升到0.9以上，最高可能需要200元才能注册一个用户），而目前BTC在实验闪电网络，速度和手续费都有所下降，目前项目组正在考虑用BTC代替EOS来进行游戏后续测验。

640.webp (3).jpg

第四个问题：EOS真的是“免费”的吗？

在以往漫长的宣传中，“免费”，一直是EOS的一大卖点。

众所周知，在POW挖矿维持的区块链系统中，矿工费是无论如何都少不了的。不管是BTC还是ETH，矿工费都不是个小数，如果是进行大额交易倒还罢了，小额交易，我买瓶水需要等半小时确认外加支付100块手续费，你是不是疯了？

POS诞生的初衷，就是为了废除浪费能源的行为，外加降低手续费。你都不挖矿，你还有什么理由收手续费啊。EOS作为POS扛旗者，一直对外号称对开发者友好，交易免费，我相信很多用户也是因为这个理由才支持EOS。

好了，从之前的描述，大家也知道了，EOS并不是如同BM宣传的那样是免费的。

我换个角度来问大家：

假设，QQ注册一个账号要你交一百块钱，那你还用QQ吗？

假设，支付宝注册一个账号要你交一百块钱，那你还用支付宝吗？

假设。百度贴吧注册一个账号要你交一百块钱。那你还玩贴吧吗？

假设。网易邮箱。一百块。玩吗？

我相信，99.9%的读者，心里只会有一个想法：

640.webp (4).jpg

在互联网上，从头上到脚下，交流、交易所有的基础设施，都是不花钱的，那凭什么你EOS就这么高贵，还得花100块才能开个账户？你有什么脸？

BM对此给出的解释是：通常一个ETH活跃账户，算他交易个20次吧，那么这20次积累的手续费肯定比在我这里注册一个账号要贵的嘛，所以我这里还是比ETH便宜多了。

我承认，当我看到BM的这番言论的时候，我真的给他气乐了。

640.webp (5).jpg

我就在想一个问题：是不是过去一年收了40亿美元，成功的让一个程序员变成了智障？或许他本来就是个智障？ETH好的地方你不学，学人家门槛高？你是不是觉得40亿美元到手了就已经后半辈子不愁了？

聪明如BM，一年挣40亿刀，这应该已经是一个程序员的巅峰了。他可能没想到，40亿美元是全球人们一点点凑出来的，其中不乏各种大佬。他现在的一举一动，每一次作死，全都被人看在眼里，如果他成功的让这些大佬的资产受损，那他的下场，会是什么样的呢？

真当收了钱就完事了？有钱为所欲为？

640.webp (6).jpg
BM名言：“30天不扩容。”

看起来，BM对自己的设计相当得意，觉得现在终于有人认可他的设计了，不然EOS-RAM怎么炒这么高？

问题是，30天后，EOS还能活吗？都说币圈一天人间一年，币圈30天，就是人间30年。30年前我刚一岁，我还尿炕加吃奶呢，30年以后的今天我身高一米八体重一百八，一拳能把一个缺乏锻炼的程序员从**打到柬埔寨，30年前的互联网还处于胚胎阶段，30年前根本就没有互联网企业，早期的互联网设施已经被当作遗迹供起来了，我请问你怎么就能保证EOS能活过这离心离德的30天？

我们可以看到，EOS-RAM采用bancor算法，BM他是从一开始就处心积虑的要炒高RAM的价格，而不是无心之失。而现在，EOS-RAM如他所愿真的炒起来了。

那么为什么EOS-RAM会涨几十倍呢？首先，币圈目前仍然是熊市，EOS跌跌不休，人们都想给自己的资产找个保值的地方；其次，EOS目前RAM市场总量是固定的，而且越往上拉盘越容易，给人一种这个东西不仅能保值而且能炒的幻象，所以，EOS-RAM如预期般的涨起来了。

那么好了。

你们现在把注册一个用户的成本推升至100块。我想请问，谁还会来注册。

EOS到底是什么，这是一个开放式的工具。如果说一个工具门槛过高，你们希望谁来跟你们一起玩？难道就你们二十来万用户在一个池塘里炒RAM玩儿？

如今的EOS-RAM已经骑虎难下。BM已经说过30天不扩容，这么多开发者摩拳擦掌准备进场又硬生生退回来，搞侧链，根本来不及，如果BM意识到危机，食言马上扩容，又面临一波政治问题：你让之前那些高价买了EOS-RAM的用户怎么办？况且EOS并不是BM一个人说了算，如果有高价囤积EOS-RAM的超级节点呢？

640.webp (7).jpg

第五个问题：我们该如何看待？

BM绝对是一个优秀的程序员。但是他可能不是一个合格的项目组织者。

从BTS开始，BM就体现出自己不适合领导一个项目的特质（见前文：EOS：具有BM特色的去中心化，还能走多远？），如今这个问题，有可能再次出现。

我们说，一个人愿望是好的，项目是好的，但是只要走错一步，就可能全盘皆输。

币圈发展太快，有时候根本来不及试错。多少竞争者觊觎着区块链3.0的王者之位，EOS脚下的路并不安稳，远未到称王称霸的时候。

要我说，有些人就是欠治。

欠被**人治。

以为自己做的比ETH好一点就无敌了，说好的免费都是空中楼阁。这个时候就应该有**人来治他。

我大胆预测：很可能在不久之后，就会出现一个和EOS很类似的产品，或者干脆就是EOS的分叉，能够比较完美的解决目前开发成本高昂的问题。如果这个产品真的来了，我会搞不犹豫的抛掉手里所有的EOS，毕竟我买入EOS不是为了陪你们这二十来万用户过家家的。

我看到BM在7月7日说，正在开发一个DRAM，是一个基于RAM的金融衍生品，希望这个DRAM能把刚需和投机者分开。对此我持观望态度。

留给EOS折腾的时间，还有多少呢？

关注公众号“区块链条”，后台回复“4”，导师将向你推荐两个可以翻五倍的币种。

沙发 jie_x57
副船长2018-7-9 15:16:20来自手机版
eos ram怎么也算是市场主导价格吧

板凳 龙辉598
水手2018-7-9 15:36:00来自手机版
sbc第一个柚子侧链主网已经上线了。

地板 区块链条
船员2018-7-9 15:43:43
引用: 龙辉598 发表于 2018-7-9 15:36
sbc第一个柚子侧链主网已经上线了。

是吗？有官网吗？

5# jimuka
船员2018-7-9 15:47:07
推荐了两个翻五倍的币是eos和bch，emmm 我觉得我的智商受到了侮辱

6# 暴饮菊花茶
水手2018-7-9 15:47:25
eos ram真正的目的是催生侧链，主链ram价格不高，谁愿意开侧链？不开侧链，tps怎么做上去。

7# 区块链条
船员2018-7-9 15:51:54
引用: 暴饮菊花茶 发表于 2018-7-9 15:47
eos ram真正的目的是催生侧链，主链ram价格不高，谁愿意开侧链？不开侧链，tps怎么做上去。

话是这么说，但是目前这个样，真的不行

8# macx1980
副船长2018-7-9 16:00:05
现在街边牵条狗都可以当
导师

9# lzyzizi
副船长2018-7-9 16:31:20
写的不错。 不过我来扮演下杠精，你问我100元注册QQ我肯定不注册，但是EOS拉个几倍，告诉你100元能进来玩EOS RAM肯定有大把人哭着喊着进来。就像一些每天写行情分析的人，开个群，入群费大几千。

10# ddd123
队长2018-7-9 17:06:10
文章结尾："很可能在不久之后，就会出现一个和EOS很类似的产品".
bts2.0还能抢救一下？

11# 区块链条
船员2018-7-9 18:27:05
引用: lzyzizi 发表于 2018-7-9 16:31
写的不错。 不过我来扮演下杠精，你问我100元注册QQ我肯定不注册，但是EOS拉个几倍，告诉你100元能进来玩EO ...

讲真 这倒不是杠精了 ，如果真是这样 交易所里注册个号就可以玩 何必去自己搞钱包呢
这样的话只会苦了那些有志于开发的人

12# 区块链条
船员2018-7-9 18:27:27
引用: lzyzizi 发表于 2018-7-9 16:31
写的不错。 不过我来扮演下杠精，你问我100元注册QQ我肯定不注册，但是EOS拉个几倍，告诉你100元能进来玩EO ...

EOS ASIA的强总开发的游戏已经准备抛弃EOS了 心寒

13# 区块链条
船员2018-7-9 18:53:04
引用: ddd123 发表于 2018-7-9 17:06
文章结尾："很可能在不久之后，就会出现一个和EOS很类似的产品".
bts2.0还能抢救一下？

bts的话，过于老旧了 感觉很难

14# 区块链条
船员2018-7-9 21:13:40
引用: jie_x57 发表于 2018-7-9 15:16
eos ram怎么也算是市场主导价格吧

你不觉得这个市场很荒谬吗

15# dujbo
副船长2018-7-9 22:14:23来自手机版
分析的很好，BM下一步是不是准备炒带宽、炒CPU？没有开发者，EOS算个屁！

16# 区块链条
船员2018-7-9 22:15:10
引用: dujbo 发表于 2018-7-9 22:14
分析的很好，BM下一步是不是准备炒带宽、炒CPU？没有开发者，EOS算个屁！

理论上只有ram这一个炒作点，但是谁知道下一步有什么新花样呢

Shit BM

please update new whitepaper

在此立贴，明年6月份EOS 价格翻10倍

                                                 by罗聪

Schema Defined DB

• What about using BSON to permit Date type and a BinData type data types storage ?
• Will there be indexes on the DB (for tables row and arrays in JSON)?
• Will the DB be able to do an action (B.E. notify change) without the need of querying (based on DB inputs not DB queries)?

Delegating Capacity

• Is it possible to define a logic based on parameters to automatically delegate capacity?

I'm translating to Italian EOS whitepaper.
Are there other documents that need a translation at the moment?

Good

在TechnicalWhitePaper中，
在“带强制性延时的消息”小节中，“而购买一个房子也许需要 72 消失的结算期“中的”消失“应该为”小时“

Virtual Machine Independent Architecture

WebAssembly
Ethereum Virtual Machine (EVM)

Why not JVM? I don't understand why ethereum need it's own VM in the first place (hard to beat JVM IMHO)

These 2 paragraphs contradict each other?

One of the major benefits of the EOS.IO software is that the amount of bandwidth available to an application is entirely independent of any token price. If an application owner holds a relevant number of tokens on a blockchain adopting EOS.IO software, then the application can run indefinitely within a fixed state and bandwidth usage. In such case, developers and users are unaffected from any price volatility in the token market and therefore not reliant on a price feed. In other words, a blockchain that adopts the EOS.IO software enables block producers to naturally increase bandwidth, computation, and storage available per token independent of the token's value.

A blockchain using EOS.IO software also awards block producers tokens every time they produce a block. The value of the tokens will impact the amount of bandwidth, storage, and computation a producer can afford to purchase; this model naturally leverages rising token values to increase network performance.

mark，2018/5/28

I was pretty surprised to see there was a whitepaper with no mention of security

1. How is the platform plan to be developed to take preventive measures against attacks?
2. What security features are expected?
3. What types of attacks might the platform be vulnerable to and what counter measures are planned to lower the risk of those attacks?

Please check whitepaper typo:
"Sometimes a smart contact behaves"
and here
https://medium.com/@mangicrypto/eos-concept-code-is-not-law-7403d3bfbe7b

Found some issues in the eosio.token docs. First off, it says transfer instead of close (transfer is there twice)

Secondly, and more important, the retire action actually isn't the opposite of create, it's the opposite of issue. This has serious implications as it's saying in the docs you can un-create a token, and that isn't the case.

I just created a token and was trying to change the supply by using the retire option, but it doesn't clear the record from the stats table, so you can't make a new token with the same name, as implied in the docs.

https://developers.eos.io/welcome/v2.2/tutorials/eosio_token/#close-action

hopefully something like this won't happen
https://decentralize.today/say-it-with-me-bitcoin-needs-a-reference-specification-76cccee61206

在 EOS.IO 软件中，区块通过 21 名生产者轮流产生。 在每一轮的开始时，21 个唯一的区块生产者被选出。 获票最高的前 20 名自动在**没轮**被选中，剩余的一个生产者通过得票比例选出。 被选中的生产者通过从区块取到的时间作为伪随机数来打乱其顺序。 打乱顺序是为确保这些生产者与其他生产者保持均衡的连通性。

首先很感谢@DayzH的无私贡献，同时也希望作者可以做的更好，尽量减少错别字，语句不通等问题。

In the official documentation, at page : https://developers.eos.io/eosio-nodeos/docs/learn-about-wallets-keys-and-accounts-with-cleos, there is a missing keyword in the cmd: cleos wallet import PRIVATE_KEY_1. The corect cmd would be : cleos wallet import --private-key PRIVATE_KEY_1

Without it the cmd does not executes successfully. Also same keyword should be added at same page, in the end of the page. Instead of : cleos wallet import 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3, it should be: cleos wallet import --private-key 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3

Please update the official documentation page. Thanks

www.google.com

With Ethereum, you can build Dapps. Why then, would you use EOS?

Update 2018-Feb-6: read https://ethresear.ch/t/against-replacing-transaction-fees-with-deposits/940/2 and https://ethresear.ch/t/initial-explorations-on-full-pos-proposal-mechanisms/925 (for the latter, particularly from "The other important topic that needs to be covered is parametrizing...").

Ethereum 1.0 isn't very scalable, however there are developments in the pipeline such as sharding, eWASM, Casper PoS and zk-STARKs (although zk-STARKs will be a few years away, probably, as they need to be optimized), that will improve its scalability while maintaining or improving security and decentralization. EOS has DPOS, which is too centralized, less secure and transaction amounts are proportional to how much EOS one holds. These trade-offs are not worth better scalability. Ethereum's approach to improving scalability while not making sacrifices is better.

Further reading: https://github.com/ethereum/wiki/wiki/Ethereum-introduction#rd

Granted, Ethereum has issues, but IMO, EOS has more.

Just read Dan's steemit post about zlib compression for smart contracts. I would suggest that either ZStandard or LZMA2 with max compression levels be used for the compression, as these will give better compression results compared to zlib.

The ZStandard license (BSD) is more friendly than tha LZMA2 license (GNU LGPL).

Having a compression type field in the smart contract data structure would allow more compression types in the future. Who knows, in 5 years a new compression type may come out that is much better than even ZStandard or LZMA2.

When adding new compression types, you would roll out the decompression support first, wait several months until everyone updates, then roll out the compression support.

If memory use is a concern, ZStandard could be used over LZMA2.

Thanks for reading and considering.

文章里有 "72 消失" ，应该是"72小时"

In the TechnicalWhitepaper.md it says "The selected producers are scheduled in an order agreed upon by 15 or more producers."
While https://developers.eos.io/welcome/latest/protocol/consensus_protocol Chapter 4.2 says it is in alphabetical order.
From what i saw, the alphabetical order is true.
Or is it just default in the EOSIO Chain that everyone agrees upon alphabetical order? Then the first statement would not be wrong at least.

          Next

Originally posted by @freddyg11 in EOSIO/eosio-web-ide#72 (comment)

All the way down，What technical problems you encountered more difficult to solve it?

eos时代来临之前留下足迹

Spanish translation says it is 100%. https://crowdin.com/project/eos-docs/es-ES

It's not in this repository, I requested access to review it and then may be add it to this repo, it's been more than week I haven't heard back from anyone.

Can anyone help me with this ?

I'm curious about the voting process. Wondering if anyone could clarify or point me in the right direction.
The documentation does not seem to be very clear on this topic

Multiple nodes are constantly receiving/losing votes. The top 21 are selected as BPs. How do we reach consensus on the BPs, I mean, votes take time to propagate, thus different nodes have different views of the world. How does EOS reconcile this information?

Let me further clarify, when processing transactions a BP emits a block with let's say 500 tx.

It's ok if your transaction was not processed at this point in time, it will probably be picked up in the next few minutes. Furthermore other BPs can easily validate the block, (the only thing a BP is interested is to prevent fraudulent txs).

Voting is different. Every vote counts, (I assume), since it takes time for information to propagate different BPs will have different views of the world.

How do BPs decide what is the correct vote count at a specific point in time when the voting process itself is so active?

https://github.com/orgs/wharfkit/projects/1/views/1

（It seems that the translator is not very familiar with EOS... The expressions are awkward and there are even some obvious mistakes... Maybe a revision is needed...）
中文版本翻译的有点问题啊，语句读起来不那么通，而且还有一些逻辑和专业词汇上的错误，最好能改正一下。

In the Whitepaper, the second image under https://github.com/EOSIO/Documentation/blob/master/TechnicalWhitePaper.md#evaluating-permissions
doesn't display.

Application developers can delegate bandwidth and computation to their users and then let the “sender pays” model enforce the usage. From the perspective of the end user it is free, but from the perspective of the blockchain it is sender-pays.

I think that above sentences are inconsistent.
"sender pays" is "end user pays".

Some Dapps may have requirement to consume data from outside world
In Ethereum, solidity allow to log a event which can be catched by ethereum software.
Ethereum software will fetch the data through rest api or other way from outside world, and then inject the result back into contract through callback function.

I am just wondering if EOS have a same way to deal with it or use other manner.

Thanks

I am sure BM will only can achieve 10% of the whitepaper In this year. All of others in it was bullshit.

Hi, why EOS producer need 45 seconds to confirm transaction when a software bug or Internet congestion? Why not 40 or 30 seconds? How to calculate the result of this?