Go/NoGo Call
June 8 0100 UTC
Note: For internal use only for the EOS Validation (EMLG) Telegram Channel. Please do not share outside of this channel.
Call to order
Proposed Agenda
Buying Ram Issue
Question: Should we accept 2/3 + 1 of the respondents in this channel for a GO/NO GO vote ?
Question: Do we accept the change to Article IX of the Constitution?
ABP Selection update from Kevin (EOS New York)
Question: Has anyone found any P0 or P1 bugs?
Voting Portal Update
Dan’s Comment: If any nodes or public endpoints are crashed, there is no real risk. We can pause the chain, block.one can debug if needed and then we can resume function. The only thing that would happen would be that those endpoints are down. These would not be fatal bugs. The only issue we can’t recover from is a massive private key breach. He does not see this as a risk factor, except for with a web wallet. Thorough vetting of web wallets will be needed to help mitigate this. Once there are recovery partners added into accounts, there will be a lot more security to maintain the safety of users.
Dan believes that if we do not print the tokens for RAM, then we would run into unforeseen issues with the Bancor algorithm that controls the RAM market. The state would not line up. Dan is working on an upgrade for the `token` contract to allow for retiring of tokens which will allow to walk back the amount of tokens.
Question: Should we “print” 19k EOS or “work out” a solution to have 1 billion flush at launch?
Dan: aBFT implementation
Timeline to implementation is currently a few months out from launch. Will need to be tested and worked through on testnets. Within a few seconds, there are already a very high level of irreversibility, 3 minutes will guarantee irreversibility. They will need to do a lot more infrastructure work to get this in, as well as IBC. There will not be a need to hardfork the chain to implement these.
48 Hour Update from Chinese Team About Security Audit
There have been no updates on this call. Currently there have been no P0s or P1s found. No further information from last call.
QUESTION: Go or No Go?
Question: If the following were true, I would change my vote to GO
-only solvable issues brought up were:
If someone needs to be added into the Validation Channel (only BPs will be accepted)
Contact:
If we cannot achieve a consensus between BPs, there may have to change to a XX amount of BPs being ready.
Next call will use a registered call on Zoom. This will allow for credentials and a poll feature.
20:57:58 From Marc-Antoine Ross EOS Canada : Here's the proposed agenda:
Re-ratify on next call the 2/3+1 for Go/NoGo
Constitution change vote + update on changes
ABP selection update
No P0 P1 reported?
Voting Portal update
Go/NoGO vote
48 hour update + coordination of the announcements
21:00:32 From Tulip Conf Proxy : Tulip Conf Proxy:
EOS Nation
EOS Cafe
EOS Meso
EOS Sillicon Valley
eosDAC
BlockEOS
EOS CSX
21:03:34 From Chitty - EOS Argentina : We can use the EOS Go checkmarks to confirm if its a valid BP or made up one
21:06:41 From ZhaoYu - EosLaoMao : Unregister users are still honoured on the new chain? Right?
21:09:24 From James Sutherland - Cypherglass : BS
21:09:45 From Josh Kauffman EOS Canada : Should we issue new tokens to pay for the amount of RAM for account creation?
21:10:00 From Igor Lins e Silva - EOS Rio : No
21:11:51 From Pete @ Block Matrix : No
21:12:38 From Eric - sw/eden : No
21:13:00 From jem proxy Rio EOSPH hkeos eoskh Acro Tribes eosviet : No
21:13:02 From wajid malik - Bitspace : Yes, users shouldn’t need to pay for RAM.
21:13:03 From nick- Eos.Fish : No
21:13:05 From Alexandre Bourget EOS Canada : Yes
21:13:05 From Adrian - SaltBlock : No
21:13:05 From Marshall - SaltBlock : No
21:13:11 From Benjamin Wang@EOShenzhen : No
21:13:15 From MAO EOSREAL : No
21:13:34 From EOS42 & EOS New York : No (EOS42 only)
21:13:41 From Tim Ogilvie - Staked : No
21:13:49 From Tim | GenerEOS : No
21:13:51 From Sebastian Castro - EOS Argentina : Yes
21:13:53 From Ross (EOSphere) : No
21:13:53 From Ben SHEOS : No
21:13:54 From cupide EOS Pacific : 发放新的token是表示 增发 么？
21:13:59 From Marc-Antoine Ross EOS Canada : Yes
21:14:00 From ZhaoYu - EosLaoMao : 对
21:14:02 From Ricardo-EOSBrazil : no
21:14:03 From ZhaoYu - EosLaoMao : 就是以前的方案
21:14:05 From hydro : yes... print it
21:14:11 From 彭赟-EosThu : yes
21:14:17 From Jorge@EOSMetal : yes
21:14:18 From Buddy Deck - EOS New York : need more information
21:14:19 From lemons@EosLaoMao : yes
21:14:19 From Roman CryptoLions : no
21:14:23 From phil : no
21:14:35 From Ravi (BlockPro) : No
21:14:35 From Yvonne@eoshenzhen : no
21:14:37 From iEdward - EOS Land : 是否需要多印1千9百多万EOS？
21:14:46 From MAO EOSREAL : 好像是19万
21:14:46 From Tim | GenerEOS : let’s wait for the proper question to be asked guys
21:14:54 From lochaiching-EOShenzhen : no
21:14:56 From phil : yes
21:15:03 From Yingxu's iPhone : yes
21:15:10 From crazybit@SuperONE.io : 议题怎么又绕回去了
21:15:26 From Benjamin Wang@EOShenzhen : Without a well-trusted "constitution," either printing money or borrow money will infringe the core value of EOS
21:15:26 From MAO EOSREAL : 是1万9千个
21:15:26 From Mr Fox@EOS WTZ : 是啊， 怎么又绕回去了
21:15:27 From Dafeng EOS Asia : 19000 tokens
21:15:30 From iEdward - EOS Land : 19万
21:15:39 From Branden Espinoza - Not a Block Producer : Is it impossible to request a loan from the public, and include a payback requirement in the BP agreement?
21:15:42 From DS Lim - EOSeoul : No
21:15:42 From Bo - EOS Silicon Valley : 1万9
21:15:48 From Dafeng EOS Asia : 19000，1万9，不是19万
21:16:05 From lemons@EosLaoMao : 我不太清楚为什么昨天不提议。
21:16:20 From Rohan - EOS Authority : that’s not possible.
21:16:27 From Rohan - EOS Authority : how did you resolve Dust?
21:16:27 From iEdward - EOS Land : 19k
21:16:53 From wajid malik - Bitspace : BM said print it.
21:17:06 From jem proxy Rio EOSPH hkeos eoskh Acro Tribes eosviet : Dust? Rounding errors? FUD.
21:18:49 From Rohan - EOS Authority : not rounding errors. the balance can not be 1 billion anyway. all the users with <1EOS was not moved into EOS anyway during the snapshot process.
21:18:52 From Igor Lins e Silva - EOS Rio : we have no need for more contracts
21:19:50 From Branden Espinoza - Not a Block Producer to Josh Kauffman EOS Canada (Privately) : Is it impossible to request a loan from the public or a whale, and include a payback requirement in the BP agreement?
21:20:31 From nagumi : zoom ID posted in bios boot again
21:21:13 From Tim | GenerEOS : guys someone posted the zoom link in the BIOS page again
21:21:23 From Tim | GenerEOS : moderators??
21:22:18 From Alexandre Bourget EOS Canada : Jem: send the commands over please...
21:22:41 From jem proxy Rio EOSPH hkeos eoskh Acro Tribes eosviet : I will dig it up, to be sure of precision.
21:22:48 From Alexandre Bourget EOS Canada : --------------------------------------------------------------
21:22:50 From Alexandre Bourget EOS Canada : --------------------------------------------------------------
21:22:50 From Alexandre Bourget EOS Canada : --------------------------------------------------------------
21:23:00 From Timothy Lewis : yes
21:23:29 From winlin-EOSBIXIN : yes, if we use the Jem method transfer token back from ram&ramfee wo should review the logical
21:24:28 From iEdward - EOS Land : 2 ABP?
21:24:35 From cupide EOS Pacific : 2 abp？
21:25:43 From phil | EOS Switzerland : we need translators
21:25:46 From Lievin - EOSYS : I think the question should be clarified again
21:26:11 From kai jing- no bp : 。
21:26:20 From Douglas Horn | EOSAmericas : Jem makes an excellent point about confusing EOS users if we issue new tokens, even with a good reason.
21:26:40 From phil | EOS Switzerland : we need to vote
21:26:41 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : please send the commands
21:26:45 From Ben SHEOS : Vote Q: Overturn previous decision to print tokens and use Jem’s method to boot - 1BN EOS tokens exactly on boot?
21:27:06 From Kurt - BPAC : Mute mics guys, lots of feedback
21:27:11 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : how are we voting on a method we don’t have?
21:27:21 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : lets see the exact commands used
21:27:21 From Alexandre Bourget EOS Canada : Douglas, the supply is increased each second on that blockchain.. no one will ever see 1B flush.. they'll see it with BP and worker proposal inflation.
21:27:29 From Timothy Lewis - LibertyBlock : Without Additional RAM cost and Additional BP rewards.
21:27:38 From Rohan - EOS Authority : can someone please make the process of not printing any more money clear? what was done? how was <1EOS not moved to EOS taken into account?
21:27:41 From phil | EOS Switzerland : people are losing faith I think its time to just go forward
21:27:53 From Marshall - SaltBlock : I think investors care very much what the supply started at
21:28:01 From Marshall - SaltBlock : Even if it's briefly
21:28:13 From cupide EOS Pacific : 没听懂第二个方案~
21:28:52 From Alexandre Bourget EOS Canada : We can destroy that supply after launch too.. only 15 need to agree at that point :P
21:29:04 From Craig@BlockSmith : on one hand, JEMs proposed method is more exact than Alex's and producers a better exact token issuance. But it's brand new and unvetted. Alex's solution with 19k tokens extra has been around for a long time and is very well tested. That's the choice we have to make. Make it perfect and risk needing yet more time, or launch and have a token balance 19k higher than 1B
21:29:14 From J.T. - EOS The World : It is pretty straight forward. The snapshot left out any public key with less than 1 EOS.
21:29:23 From Nate D - Aloha EOS : Perhaps the question could be “Should we try a new method of paying for ram in an effort to get the EOS supply to exactly 1 billion”
21:29:57 From Alexandre Bourget EOS Canada : Jem: I PM'd you on Telegram
21:30:04 From Alex - EOS SOCAL : additionally, investors have expected more than 500k new eos in circulation by today if wed launched last weekend.
21:30:10 From J.T. - EOS The World : Snapshot was 996690656.5 EOS
21:30:15 From jem proxy Rio EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : During injection, we pay for RAM for each account creation using eosio. These payments go into the system accounts eosio.ram and eosio.ramfee. After injection of the full snapshot, 19,832.9750 EOS are in the eosio.ram system account, and 95.5916 EOS are in the eosio.ramfee system account.
Just prior to the resignation of the eosio account during the boot process, the entire amount from both of these accounts are transfered to the eosio account, leaving both with a balance of zero.
By this method, the correct amounts exist in all system account, no RAM fees are charged to user accounts, and the total supply at launch is set to exactly 1B EOS.
21:30:15 From Alex - EOS SOCAL : so 19k is trivial
21:30:20 From gustavomick-eosargentina : Remember Dan answer about this.
21:30:26 From Angelia@EosStore : 1 方案 比较简单
21:30:27 From Marshall - SaltBlock : That's a good point about the snapshot
21:30:27 From Timothy Lewis - LibertyBlock : Alex, investors expected nothing until a proper chain was launched.
21:30:36 From Timothy Lewis - LibertyBlock : They expected a proper chain.
21:30:43 From phil | EOS Switzerland : dan is frustrated we need to think clearly about this, so much money is on the line
21:31:01 From James Sutherland - Cypherglass : ```Shall we switch from the print method to the Jem transfer method to pay for account creation?```
21:31:01 From jem proxy Rio EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Dan is wrong about this. Token holders do care.
21:31:30 From Alex - EOS SOCAL : That said, if Jems proposed solution works as said, I see no reason to print
21:31:37 From Mr Fox@EOS WTZ : so 19k is trivial
21:31:39 From Miłosz Eos Emerge Poland : Did Dan elaborate on this token print scenario in any way?
21:31:48 From Mr Fox@EOS WTZ : Just vote for it
21:31:52 From Mathieu - EOS Canada : Should we try a new untested method of paying for ram in an effort to get the EOS supply to exactly 1 billion?
21:32:26 From Douglas Horn | EOSAmericas : Alexandre - I disagree. There will be enough people able to monitor this who will know and spread the word. Remember DASH? People are still talking about the accidental premine years later. It’s an issue that never really goes away and it erodes belief in the chain.
21:32:26 From Celu - Blockgenic : whichever way we choose lets just make sure we do it in a timley manner
21:32:31 From david : As long as the 19K tokens can be reconciled later, then we should go. More important for investors to move forward as long as the 19K can be accounted for later
21:32:51 From yino : Put the 19000 EOS in the 4% issuance of the first year?
21:33:45 From jem proxy Rio EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : During injection, we pay for RAM for each account creation using eosio. These payments go into the system accounts eosio.ram and eosio.ramfee. After injection of the full snapshot, 19,832.9750 EOS are in the eosio.ram system account, and 95.5916 EOS are in the eosio.ramfee system account.
Just prior to the resignation of the eosio account during the boot process, the entire amount from both of these accounts are transfered to the eosio account, leaving both with a balance of zero.
By this method, the correct amounts exist in all system account, no RAM fees are charged to user accounts, and the total supply at launch is set to exactly 1B EOS.
21:34:02 From Douglas Horn | EOSAmericas : The general EOS tokenholders (including those of the future) do not understand these subtle points.
21:34:02 From Timothy Lewis - LibertyBlock : We are effectively charing those that Airdrop more by default from this point forward.
21:34:06 From James Sutherland - Cypherglass : suggested question, "Shall we switch from the print method to the Jem transfer method to pay for account creation?"
21:34:24 From Aaron (Greymass) : In terms of optics, what damages public perception more: a ~0.002% increase in initial supply vs an indeterminate delay in the launch of EOS.
21:34:33 From Douglas Horn | EOSAmericas : Optics are important!
21:34:49 From Timothy Lewis - LibertyBlock : Do it right or choose to just do it.
21:35:00 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : no - tulip conf proxy
21:35:03 From Sebastian Castro - EOS Argentina : No
21:35:10 From david : Optics are easy - LAUNCH!! Just as long as the 19K can be accounted for later
21:35:10 From Douglas Horn | EOSAmericas : Kick out phone numbers.
21:35:12 From phil | EOS Switzerland : yes - eos swiss
21:35:17 From Timothy Lewis - LibertyBlock : Yes
21:35:22 From winlin-EOSBIXIN : the most important thins is which tool can by used now and have validatied by other bps
21:35:25 From Tim | GenerEOS : kick them out we can’t even see their names
21:35:33 From Buddy Deck - EOS New York : it doesn't matter we can validate using the same tools.
21:35:41 From tmuskal @ LiquidEOS : no
21:35:43 From Mathieu - EOS Canada : ————————————————————————————————————————————————————Should we try a new untested method of paying for ram in an effort to get the EOS supply to exactly 1 billion
21:35:45 From Alexandre Bourget EOS Canada : -------------------------------------------------------------------------
_____________________________________________________
_____________________________________________________
"Shall we switch from the print method to the Jem transfer method to pay for account creation?
21:35:51 From Tim | GenerEOS : no
21:35:52 From Timothy Lewis - LibertyBlock : Yes, do it right.
21:35:53 From Alexandre Bourget EOS Canada : No
21:35:53 From jem proxy Rio EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Yes
21:35:53 From winlin-EOSBIXIN : NO
21:35:54 From Jialin@EOS WTZ : No
21:35:54 From Aaron (Greymass) : no
21:35:55 From James Sutherland - Cypherglass : No
21:35:55 From phil | EOS Switzerland : yes
21:35:56 From Shah@BlockSmith : no
21:35:57 From Craig@BlockSmith : no, do not switch, print 19k
21:35:57 From Roman CryptoLions : yes
21:35:58 From ZhaoYu - EosLaoMao : no
21:35:58 From Tim Ogilvie - Staked : No
21:35:58 From Marc-Antoine Ross EOS Canada : no
21:35:59 From Jorge@EOSMetal : no
21:35:59 From Buddy Deck - EOS New York : yes
21:35:59 From Ralf | GenerEOS : No
21:35:59 From santhosh - EOSNodeOne : no
21:36:00 From Jacky - JEDA : no
21:36:00 From wajid malik - Bitspace : No
21:36:01 From lemons@EosLaoMao : no
21:36:01 From Marshall - SaltBlock : yes
21:36:01 From Issay Tseng@OracleChain : NO
21:36:01 From Ross (EOSphere) : No
21:36:01 From nick- Eos.Fish : Yes, Switch to Jem method
21:36:01 From Nate D - Aloha EOS : no
21:36:01 From Dr Ye - EOS WashingtonDC - TChain : no
21:36:01 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : no - tulip conf
21:36:02 From song : no
21:36:04 From Dafeng EOS Asia : no
21:36:04 From Rohan - EOS Authority : no. don’t switch
21:36:05 From admin : no
21:36:06 From Bean - EOS Cannon : no
21:36:07 From zhengyu@infinitystones - EOS Danhua : yes
21:36:07 From Rob - Worbli : no
21:36:08 From Bo - EOS Silicon Valley : No
21:36:09 From Yasong “matt” Shi UnlimitedEOS : YES
21:36:09 From Leeroy Jenkins : no
21:36:12 From Ben SHEOS : Yes
21:36:12 From Rick Schlesinger - EOS New York : no
21:36:13 From Sharif - EOS Dublin : No
21:36:15 From Douglas Horn | EOSAmericas : No to creating new tokens.
21:36:15 From Lievin - EOSYS : No
21:36:15 From Alex - EOS SOCAL : no
21:36:15 From EOS42 & EOS New York : yes (EOS42)
21:36:16 From Gordo - HelloEOS : no
21:36:16 From Miłosz Eos Emerge Poland : no
21:36:16 From Sebastian Castro - EOS Argentina : No
21:36:17 From Pete @ Block Matrix : yes
21:36:18 From Pascal | EOS Network : No
21:36:19 From Emily - shEOS : yes
21:36:22 From MAO EOSREAL : yes
21:36:24 From Adrian - SaltBlock : yes
21:36:24 From Ravi (BlockPro) : no
21:36:25 From admin : safe best no
21:36:25 From Issay Tseng@OracleChain : yes
21:36:27 From phil | EOS Switzerland : yes
21:36:28 From Igor Lins e Silva - EOS Rio : yes
21:36:31 From deadlock - EOSIO.SG : YES
21:36:36 From Nathan (GenerEOS) : no
21:36:37 From J.T. - EOS The World : Yes
21:36:38 From Jason-EOS Pacific : no
21:36:40 From Eric - sw/eden : Yes - switch
21:36:44 From MEET.ONE : YES.
21:36:47 From Yvonne@eoshenzhen : yes
21:36:48 From Patrick Hajek eosarmy : no
21:36:50 From khosi - eosAfrica : Yes
21:36:50 From guillaume@eostitan.com : yes
21:36:56 From Yves La Rose - EOS Nation : no
21:36:58 From Ricardo-EOSBrazil : yes of course. 1bi is 1bi
21:37:04 From crazybit@SuperONE.io : We cannot make not fully tested change before lauching
21:37:08 From 彭赟-EosThu : no
21:37:10 From Alexandre Bourget EOS Canada : Jem: still waiting on the two commands you say are trivial. Maybe we have a quick fix here.
21:37:13 From Douglas Horn | EOSAmericas : Sorry. Yes to the Jem method.
21:37:21 From eostark : jem method. do it right
21:37:21 From phil | EOS Switzerland : wait I understand the question wrong
21:37:25 From phil | EOS Switzerland : can we do it again
21:37:33 From lochaiching-EOShenzhen : Yes
21:37:36 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : It is two transfer commands
21:37:49 From Hubert@EOSeoul : yes
21:37:52 From Issay Tseng@OracleChain : YES
21:38:05 From Issay Tseng@OracleChain : Yes - switch
21:38:05 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : 1. Eosio.ram -> eosin 2. eosio.ramfee->eosio
21:38:07 From Benjamin Wang@EOShenzhen : Yes - switch
21:38:16 From Eric - sw/eden : It seems a lot of people didn't understand that the negation of the question was added in there since the last vote.
21:38:20 From py@eos.cybex : No, last min change before going live is a big no in software engineering, even its trivial
21:38:20 From Bean - EOS Cannon : sorry. YES
21:38:32 From Swandoyo@EOS Cafe Calgary : Yes - EOS Cafe Calgary
21:38:37 From phil | EOS Switzerland : -------------------------------------------------------------------------
_____________________________________________________
_____________________________________________________
"Shall we keep the print method instead of the Jem transfer method to pay for account creation?" <- this is better wording
21:38:41 From Alexandre Bourget EOS Canada : Jem: what about doing that operation right after 15% unlock ?
21:38:44 From phil | EOS Switzerland : vote again
21:38:54 From andrew - EOS JRR : YES
21:39:06 From Douglas Horn | EOSAmericas : Need to vote again.
21:39:18 From Tim | GenerEOS : let’s vote again
21:39:19 From Rohan - EOS Authority : are there any other items to vote on?
21:39:21 From Thomas Cox (not a BP) : Vote with the words "PRINT" or "TRANSFER"
21:39:27 From Ricardo-EOSBrazil : TRANSFER
21:39:30 From py@eos.cybex : Print
21:39:32 From Tim | GenerEOS : print or transfer
21:39:38 From Timothy Lewis - LibertyBlock : 1b
21:40:02 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Alex, best done before resignation. Immediately after 15% means it is way down in the chain, well after reproducer and voting entries.
21:40:30 From Timothy Lewis - LibertyBlock : Transfer
21:40:36 From Kyunghwan Kim - EOSeoul : Best done before resignation. +1
21:41:38 From Rohan - EOS Authority : Keep it open. show everyone the code please.
21:42:02 From phil | EOS Switzerland : it does not matter, imo
21:42:03 From crazybit@SuperONE.io : PRINT IT, please be noted that there would be more 500K EOS generated now instead of 19K if we launched last Friday.
21:42:07 From Eric - sw/eden : Transfer - keep supply at 1 billion
21:42:15 From Tim | GenerEOS : remember what Dan said?? Print
21:42:19 From Issay Tseng@OracleChain : TRANSFER
21:42:22 From Pete @ Block Matrix : Transfer
21:42:26 From phil | EOS Switzerland : we should not treat dan as gospel!
21:42:27 From Leeroy Jenkins : Yup
21:42:28 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : no
21:42:32 From EOS42 & EOS New York : Transfer (EOS42)
21:42:32 From Lars Ihler - Bitspace : well what is the facts then..
21:42:33 From tmuskal @ LiquidEOS : print. not a good enough reason to delay or introduce last minute changes.
21:42:37 From Douglas Horn | EOSAmericas : This is important
21:42:40 From Miłosz Eos Emerge Poland : transfer
21:42:40 From Lars Ihler - Bitspace : There is also issues regarding constitution
21:42:41 From phil | EOS Switzerland : EOS is about us, not dan
21:42:42 From Edgar@EOS Costa Rica : print
21:42:44 From Yvonne@eoshenzhen : Transfer（eoshenzhen）
21:42:46 From Jialin@EOS WTZ : Print
21:42:50 From Aaron (Greymass) : Print
21:42:51 From wajid malik - Bitspace : not show stopper
21:42:55 From nick- Eos.Fish : Transfer - I think we should stick to 1 Billion
21:42:58 From superbigfu@EOSWenzhou : print
21:43:00 From winlin-EOSBIXIN : print
21:43:03 From phil | EOS Switzerland : transfer
21:43:19 From Hubert@EOSeoul : Transfer
21:43:26 From eostark : transfer
21:43:28 From Sebastian Castro - EOS Argentina : Print
21:43:34 From david : Look, it is not statistically significant, we have an over-under / roundoff daily if need be
21:43:36 From crazybit@SuperONE.io : People are watching us, the token holders are waiting us.
21:43:38 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : ##### RAM Market Compensation
ramtokens=(./cleos.sh get table eosio.token eosio.ram accounts | jq -r ".rows[0].balance")
./cleos.sh transfer eosio.ram eosio '\"'"$ramtokens"'\"' "ram payback";
ramfee=(./cleos.sh get table eosio.token eosio.ramfee accounts | jq -r ".rows[0].balance")
./cleos.sh transfer eosio.ramfee eosio '\"'"$ramfee"'\"' "ramfee payback";
21:43:39 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : good idea
21:43:48 From Josh Kauffman EOS Canada : ____________
21:43:48 From santhosh - EOSNodeOne : print
21:43:48 From Josh Kauffman EOS Canada : Re-ratify on next call the 2/3+1 for Go/NoGo
Constitution change vote + update on changes
ABP selection update
No P0 P1 reported?
Go/NoGo vote
48 hour update
Voting Portal update
21:46:01 From Issay Tseng@OracleChain : 19w is a not small amount,we thought we should let the token holder to vote the print/noPrint proposal
21:46:03 From Rohan - EOS Authority : ok everyone. Rohan from EOS Authority here. The actual total from the snapshot is
21:46:06 From Rohan - EOS Authority : 999,991,899.197
21:46:22 From Rohan - EOS Authority : we are 9000 short with Dust already
21:46:52 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Yes, 9k short from “dust”. We make initial supply 1B, so that dust remain in eosio account.
21:46:54 From Rohan - EOS Authority : this amount above includes registered and unregistered. the rest was dust <1EOS
21:47:08 From Dr Ye - EOS WashingtonDC - TChain : what is the risk of staying status quote and move on?
21:47:12 From Douglas Horn | EOSAmericas : Could each BP candidate just stake a few hundred EOS tokens so we are borrowing from ourselves?
21:47:24 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : No need to borrow.
21:47:39 From Rohan - EOS Authority : how does that work?? which account gets the 9K that was originally short if you increase supply to 1B?
21:47:42 From Tim | GenerEOS : we have already voted on this in the last meeting. if we are going to keep revisiting previously voted on issues we will keep going in circles
21:47:48 From Rohan - EOS Authority : isn’t that inflation then?
21:47:50 From Lars Ihler - Bitspace : Where did the "Dust" go?
21:48:07 From Tim | GenerEOS : it has been voted on let’s move on
21:48:10 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : No account “gets” it. It is excess in eosio, not allocatable.
21:48:47 From Ben SHEOS : let’s vote on whether or not to consider Jem’s approach as an option.
21:48:58 From Alex - EOS SOCAL : That was the plan to begin with no? BPs handle the 19k right away
21:49:05 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : yes
21:49:31 From Rohan - EOS Authority : checkout eosauthority.com/genesis
21:50:20 From Rohan - EOS Authority : OK guys. if we aim for optics 999,991,899.197 should be the amount moved into EOS main net. nothing more
21:50:34 From Rohan - EOS Authority : if we don’t care about optics. we then just print more
21:50:54 From Edward - EOS Land : move on
21:51:04 From Igor Lins e Silva - EOS Rio : agree Rohan
21:51:09 From david : Right — So bottom line, it is just nuts to wait until EVERYTHING is perfect. These 9K tokens can be handled by a roundoff account.
21:51:09 From Marc-Antoine Ross EOS Canada : —————————————
21:51:10 From Marc-Antoine Ross EOS Canada : Should we accept 2/3 + 1 of the respondents in this channel for a GO/NO GO vote ?
21:51:10 From phil | EOS Switzerland : there is a problem - it looks like a korean may found a high severity bug in the code - hold on getting more info
21:51:11 From Sebastian Castro - EOS Argentina : I wonder which method token holders will prefer… Free Token or Stuck Memory Tokens.
21:51:17 From Marc-Antoine Ross EOS Canada : ——————————————————————
21:51:18 From Marc-Antoine Ross EOS Canada : Should we accept 2/3 + 1 of the respondents in this channel for a GO/NO GO vote ?
21:51:21 From Marc-Antoine Ross EOS Canada : ——————————————————————
21:51:23 From Alex - EOS SOCAL : Yes
21:51:23 From Ross (EOSphere) : Yes
21:51:24 From Tim | GenerEOS : yes
21:51:24 From Sharif - EOS Dublin : Yes
21:51:25 From Lievin - EOSYS : Yes
21:51:25 From Buddy Deck - EOS New York : yes
21:51:25 From Alexandre Bourget EOS Canada : Yes
21:51:26 From khosi - eosAfrica : Yes
21:51:26 From Marc-Antoine Ross EOS Canada : Yes
21:51:27 From ZhaoYu - EosLaoMao : yes
21:51:27 From Tim Ogilvie - Staked : Yes
21:51:27 From Rick Schlesinger - EOS New York : yes
21:51:28 From phil | EOS Switzerland : *korea auditing co
21:51:28 From Miłosz Eos Emerge Poland : yes
21:51:28 From Pete @ Block Matrix : yes
21:51:30 From Dafeng EOS Asia : Yes
21:51:30 From Timothy Lewis - LibertyBlock : YES
21:51:31 From Marshall - SaltBlock : Yes
21:51:32 From Rob - Worbli : yes
21:51:32 From Pascal | EOS Network : yes
21:51:32 From Jorge@EOSMetal : yes
21:51:32 From Swandoyo@EOS Cafe Calgary : Yes
21:51:33 From Nate D - Aloha EOS : YES
21:51:33 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : yes
21:51:34 From Shah@BlockSmith : Yes
21:51:35 From Adrian - SaltBlock : yes
21:51:35 From simon EOS Store : yes
21:51:37 From James Sutherland - Cypherglass : yes
21:51:38 From Sam @ EOS Dublin : Yes
21:51:39 From deadlock - EOSIO.SG : yes
21:51:39 From Yasong “matt” Shi UnlimitedEOS : YES
21:51:39 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : yes
21:51:39 From Bean - EOS Cannon : yes
21:51:39 From Hank@EOS Palliums : yes
21:51:41 From Ricardo-EOSBrazil : yes
21:51:44 From Gordo - HelloEOS : yes
21:51:45 From phil | EOS Switzerland : yes
21:51:45 From Peter Bue EOS Americas : yes
21:51:46 From J.T. - EOS The World : Yes
21:51:46 From Sebastian Castro - EOS Argentina : Yes
21:51:48 From Jialin@EOS WTZ : yes
21:51:49 From Ravi (BlockPro) : yes
21:51:50 From Edgar@EOS Costa Rica : yes
21:51:50 From MAO EOSREAL : Yes
21:51:51 From heejae : yes
21:51:51 From andrew - EOS JRR : yes
21:51:52 From Ralf | GenerEOS : yes
21:51:55 From EOS42 & EOS New York : yes (EOS42)
21:51:57 From wajid malik - Bitspace : yes
21:51:59 From Jacky - JEDA : YES
21:52:00 From Marek Eos Emerge Poland : yes
21:52:00 From Eric - sw/eden : Yes
21:52:01 From tmuskal @ LiquidEOS : yes
21:52:02 From santhosh - EOSNodeOne : yes
21:52:04 From Ben SHEOS : yes
21:52:05 From eostark : yes
21:52:06 From Emily - shEOS : Yes
21:52:06 From Rohan - EOS Authority : yes
21:52:09 From Hubert@EOSeoul : yes
21:52:10 From 6772139 : yes
21:52:13 From Roman CryptoLions : yes - but we need to vet non-BP attendees
21:52:14 From nick- Eos.Fish : Yes
21:52:19 From Dafeng EOS Asia : yes
21:52:20 From Kevin@EOS Galaxy : Yes
21:52:21 From crazybit@SuperONE.io : yes, gogogo
21:52:22 From Issay Tseng@OracleChain : YES
21:52:22 From Douglas Horn | EOSAmericas : Yes
21:52:24 From 彭赟-EosThu : yes
21:52:24 From VC@EOS Gravity : ye s
21:52:24 From Celu - Blockgenic : yes
21:52:25 From david : YES
21:52:31 From Leeroy Jenkins : no
21:52:32 From Shane EOS Pacific : yes
21:52:38 From Joshua Qiu@EOSeco : yes
21:52:42 From zhengyu@infinitystones - EOS Danhua : yes
21:52:44 From Mr Fox@EOS WTZ : yes
21:52:53 From Edward - EOS Land : yes
21:52:55 From Craig@BlockSmith : yes
21:52:58 From Mr Fox@EOS WTZ : yes
21:52:59 From EOSWenzhou : Yes
21:54:33 From Sebastian Castro - EOS Argentina : yes
21:54:34 From Roman CryptoLions : Forum post: https://forums.eosgo.io/discussion/1189/the-case-for-reverting-article-ix-9#latest
21:54:44 From Tim Ogilvie - Staked : Can you provide some context as to why ECAF is preferable?
21:54:56 From Alexandre Bourget EOS Canada : ---------------------------------------------------
---------------------------------------------------
---------------------------------------------------
Shall we revert the article 9 language in the Consititution to restore ECAF as the default arbitration forum, not ICC ?
21:54:59 From Alex - EOS SOCAL : yes
21:55:01 From Buddy Deck - EOS New York : yes
21:55:02 From Nate D - Aloha EOS : yes
21:55:03 From Marshall - SaltBlock : Yes
21:55:05 From Douglas Horn | EOSAmericas : yes
21:55:05 From Marc-Antoine Ross EOS Canada : Yes
21:55:06 From Jorge@EOSMetal : yes
21:55:07 From Ben SHEOS : Yes
21:55:07 From Yves La Rose - EOS Nation : yes to revert to ecaf
21:55:08 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : MUCH YES - Tulip Conf Proxy
21:55:10 From Lievin - EOSYS : Yes
21:55:12 From Celu - Blockgenic : yes
21:55:13 From Igor Lins e Silva - EOS Rio : yes
21:55:13 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Yes
21:55:13 From Patrick Hajek eosarmy : yes
21:55:15 From wajid malik - Bitspace : yes
21:55:17 From Edgar@EOS Costa Rica : yes ecaf
21:55:18 From Pete @ Block Matrix : yes
21:55:19 From Roman CryptoLions : yes
21:55:22 From Rohan - EOS Authority : Yes
21:55:24 From Alexandre Bourget EOS Canada : yes, ECAF all the way
21:55:26 From ZhaoYu - EosLaoMao : yes
21:55:26 From J.T. - EOS The World : Yes
21:55:26 From nick- Eos.Fish : Yes
21:55:27 From Rick Schlesinger - EOS New York : yes ECAF
21:55:30 From Ross (EOSphere) : Yes
21:55:30 From Sharif - EOS Dublin : Yes
21:55:32 From Yvonne@eoshenzhen : https://forums.eosgo.io/discussion/1189/the-case-for-reverting-article-ix-9/p1?new=1
21:55:42 From TrucNguyen : yes
21:56:07 From Nathan (GenerEOS) : yes
21:56:08 From Benjamin Wang@EOShenzhen : yes
21:56:12 From Eric - sw/eden : Yes
21:56:13 From Dafeng EOS Asia : https://github.com/EOS-Mainnet/governance/pull/15
21:56:15 From Dafeng EOS Asia : Yes
21:56:16 From Adrian - SaltBlock : yes
21:56:17 From guillaume@eostitan.com : yes
21:56:19 From deadlock - EOSIO.SG : yes
21:56:30 From tmuskal @ LiquidEOS : yes
21:56:37 From Hubert@EOSeoul : yes
21:56:41 From Weifeng@EOS.LAWYER : yes
21:56:45 From winlin-EOSBIXIN : YES
21:56:49 From Craig@BlockSmith : yes rever as TCox is advising us to do
21:56:49 From Timothy Lewis - LibertyBlock : YES ECAF
21:56:54 From Jialin@EOS WTZ : yes
21:56:58 From Swandoyo@EOS Cafe Calgary : Yes for ECAF
21:56:58 From phil | EOS Switzerland : yes
21:57:16 From andrew - EOS JRR : yes
21:57:17 From Ricardo-EOSBrazil : yes
21:57:27 From Jacky - JEDA : yes
21:57:36 From Bo - EOS Silicon Valley : Yes
21:57:38 From James Sutherland - Cypherglass : Yes
21:57:40 From Kevin@EOS Galaxy : Yes
21:57:42 From MAO EOSREAL : Yes
21:57:42 From Rob - Worbli : yes
21:57:43 From Marek Eos Emerge Poland : yes
21:57:43 From Bean - EOS Cannon : yes
21:57:44 From VC@EOS Gravity : Yes
21:57:46 From Ravi (BlockPro) : yes
21:57:46 From Gordo - HelloEOS : yes
21:57:47 From Yvonne@eoshenzhen : yes ECAF
21:57:48 From Issay Tseng@OracleChain : Yes
21:57:49 From Albert-EosThu : yes
21:57:50 From simon EOS Store : yes
21:57:55 From Mr Fox@EOS WTZ : yes
21:57:55 From Edward - EOS Land : yes, ECAF
21:57:59 From khosi - eosAfrica : Yes
21:58:00 From Pascal | EOS Network : Yes
21:58:42 From admin : no
22:00:57 From Douglas Horn | EOSAmericas : Can’t we tell the country by IP address?
22:01:15 From Alex - EOS SOCAL : they could be on the cloud
22:01:27 From Douglas Horn | EOSAmericas : Maybe better to just use the last two numbers of the IP address?
22:01:47 From Douglas Horn | EOSAmericas : Or to create a random token for each one
22:03:05 From Sebastian Castro - EOS Argentina : Yes
22:03:25 From Tim | GenerEOS : Thanks Kevin!
22:03:48 From jem proxy EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : https://github.com/EOSIO/eos/issues/3917 and https://github.com/EOSIO/eos/issues/3918
22:05:27 From Douglas Horn | EOSAmericas : That is a pretty big problem. We need to understand it.
22:05:36 From guillaume@eostitan.com : +1
22:05:52 From phil | EOS Switzerland : that is a major problem indeed
22:05:59 From Aaron (Greymass) : It’s a wallet issue, not consensus.
22:06:08 From phil | EOS Switzerland : ugh, is anyone else disheartened at the amount of bugs so far?
22:06:10 From J.T. - EOS The World : What was the issue Korea found?
22:06:10 From Igor Lins e Silva - EOS Rio : that may cause confusion to a lot of users
22:06:19 From Alex - EOS SOCAL : +1
22:06:19 From phil | EOS Switzerland : im awaiting response
22:06:20 From Douglas Horn | EOSAmericas : It’s a product of DPoS. A big concern for systems with pre-selected validators.
22:06:34 From phil | EOS Switzerland : all i got was a short memo
22:07:25 From Douglas Horn | EOSAmericas : Any BP could conceivably create a double-spend. I don’t think any would, but it errodes faith in the system.
22:07:56 From Douglas Horn | EOSAmericas : It’s an existential issue.
22:08:51 From Aaron (Greymass) : If it’s not in the LIB, it’s not guaranteed to be there.
22:09:35 From Edward - EOS Land : Is it p0 or p1 issue?
22:09:40 From Douglas Horn | EOSAmericas : P0
22:09:59 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : Tulip Conf is out! (security is closing the building)
22:10:01 From Igor Lins e Silva - EOS Rio : the API should respond something more explicit
22:10:08 From Tulip Conf Proxy |Nation|Cafe|Meso|Sillicon|DAC|Block|CSX : We will get back online soon
22:10:15 From phil | EOS Switzerland : these are complex issues
22:10:16 From Igor Lins e Silva - EOS Rio : https://github.com/EOSIO/eos/issues/3918#issuecomment-395543887 and this?
22:11:30 From Aaron (Greymass) : I’d like to point out that these new blacklist/whitelist parameters BPs will be able to specify, when used, will create this exact same UX for someone trying to issue a transaction.
22:11:32 From Tim | GenerEOS : Is it a showstopper?
22:13:24 From Tim | GenerEOS : agree
22:14:15 From phil | EOS Switzerland : i think this is what the korean auditors were referencing
22:14:20 From Tim | GenerEOS : listen to Dan
22:14:20 From Aaron (Greymass) : It’s in the wild on every one of these DPOS blockchains
22:14:26 From phil | EOS Switzerland : except they claimed it can produce 'shadow transactions' which are never visible on the network
22:14:35 From Douglas Horn | EOSAmericas : Is Dan a part of this conversation or not? If so he should be on the call.
22:14:38 From phil | EOS Switzerland : waiting for a more detailed explanation, they say p1
22:14:46 From Timothy Lewis - LibertyBlock : Wait for analysis
22:15:14 From phil | EOS Switzerland : it all falls back on transaction propagation issue
22:15:17 From Chitty - EOS Argentina : Net has been tested in jungle and aurora
22:15:20 From Chitty - EOS Argentina : bnet
22:15:43 From Igor Lins e Silva - EOS Rio : why bnet would fix this?
22:15:45 From Tim | GenerEOS : Take a vote. Showstopper or not?
22:16:18 From Rohan - EOS Authority : Not blocker. Agreed with Dan.
22:16:20 From phil | EOS Switzerland : yes
22:16:32 From Tim | GenerEOS : Yes agree with Dan
22:16:37 From Lars Ihler - Bitspace : Article III is broken.
22:16:43 From Yingxu's iPhone : showstopper
22:17:20 From Bo - EOS Silicon Valley : https://zoom.us/j/326472166
22:17:27 From Douglas Horn | EOSAmericas : Showstopper
22:18:02 From phil | EOS Switzerland : yes we need to be firm and confident
22:18:07 From phil | EOS Switzerland : no
22:18:09 From phil | EOS Switzerland : no time
22:18:12 From phil | EOS Switzerland : that is trivial
22:18:25 From Tim | GenerEOS : just delete some phone numbers off
22:18:35 From J.T. - EOS The World : Whats the youtube links?
22:18:39 From Douglas Horn | EOSAmericas : Let’s all call that number!
22:18:48 From nick- Eos.Fish : Should be able to tell from the stream. Whats the link?
22:19:04 From Tim | GenerEOS : kick them all without BP name
22:19:34 From phil | EOS Switzerland : +1 tim
22:19:47 From Peter Bue EOS Americas : lol
22:19:52 From gustavomick-eosargentina : also we can consult about print vs transfer
22:20:33 From Tim | GenerEOS : delete away
22:20:49 From gustavomick-eosargentina : Dan is already here
22:21:04 From Michael EOS Pacific : Dan
22:21:06 From phil | EOS Switzerland : welcome dan
22:21:12 From Michael EOS Pacific : where is your cat
22:21:18 From Weifeng@EOS.LAWYER : welcome dan
22:21:22 From Edgar@EOS Costa Rica : welcome Dan!
22:21:38 From Edward - EOS Land : nice to have Dan here
22:21:48 From zformular@EOSBepal : welcome Dan
22:22:09 From guillaume@eostitan.com : https://github.com/EOSIO/eos/issues/3918
22:22:44 From phil | EOS Switzerland : i cant hear fully, can you speak a little louder dan
22:23:00 From phil | EOS Switzerland : thank you that is better
22:23:27 From Alex : you can observe this behavior at Bios boot chain now
22:25:10 From kedar - LibertyBlock : not a showstopper. this bug is avoidable with proper procedures and isn't at the chain level
22:25:38 From phil | EOS Switzerland : Dan - a korean auditor was looking into this bug and thinks that it may have a larger impact than you seem to feel
22:25:52 From Weifeng@EOS.LAWYER : let's launch the eos main net, too many eos holders are waiting
22:26:11 From Edward - EOS Land : Dan说3918不是P0或P1的bug
22:27:03 From phil | EOS Switzerland : that is the 'shadow transaction'
22:27:06 From MAO EOSREAL : 然后又做了一个test贴上去，dan在看
22:29:20 From Greg | EOSsxsw : from the Korean auditors:
퍼지 일치가 그림자 트랜잭션을 생성합니다
22:29:31 From phil | EOS Switzerland : couldn't this result in people sending more than they desire?
22:29:33 From Timothy Lewis - LibertyBlock : translation?
22:29:41 From MAO EOSREAL : Dan说会继续看，而且会修，但不是大问题
22:29:44 From Lievin - EOSYS : P0: Do not do anything else, this is a blocker.
P1: Must be fixed.
P2: Should be fixed, time and resource permitting.
P3: Might get fixed.
P4: Noted for future.
22:29:45 From Weifeng@EOS.LAWYER : is not a critical problem, just a unpolished behavior
22:30:09 From Marek Eos Emerge Poland : Great let move on
22:30:29 From Douglas Horn | EOSAmericas : I would add an issue that severely undermines user confidence in the system
22:30:44 From Eric - sw/eden : > Dan - a korean auditor was looking into this bug and thinks that it may have a larger impact than you seem to feel
Phil: Could you expand?
22:31:00 From Lars Ihler - Bitspace : Please expand
22:31:07 From Greg | EOSsxsw : 이 문제는 쇼 마개처럼 들린다
22:31:19 From Edward - EOS Land : Dan说不是showstopper bug
22:31:23 From Devin Lee : Who's Korean auditor?
22:31:34 From Block Lord l EOSindia : what is this new bug about
22:31:44 From heejae - EOSYS : 22 Who is the Korean editor?
22:31:46 From Block Lord l EOSindia : what is level of severity
22:32:23 From phil | EOS Switzerland : lets let dan talk
22:32:56 From Sharif - EOS Dublin : Should we ask Dan to comment on Ram issue we discussed at the start of the call ???
22:33:05 From Weifeng@EOS.LAWYER : yes. totally agree with dan
22:33:14 From Tim | GenerEOS : yes Sharif
22:33:24 From Douglas Horn | EOSAmericas : Yes
22:33:26 From Timothy Lewis - LibertyBlock : If he is given the discussion of the solution, yes
22:33:26 From Weifeng@EOS.LAWYER : there is no private key breach, and we can launch the chain.
22:34:56 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : User expectations need to be set, finalization time is minutes, not seconds, for now. Portals and apps need to take this into account. We have an education job ahead of us.
22:35:08 From davidmoss : Agreed
22:35:15 From Alex - EOS SOCAL : agreed
22:35:20 From Sebastian Castro - EOS Argentina : agreed
22:35:25 From Block Lord l EOSindia : what is this private key brea
22:35:26 From lochaiching-EOShenzhen : agreed
22:35:31 From Block Lord l EOSindia : breach*
22:35:35 From phil | EOS Switzerland : https://www.kisa.or.kr/main.jsp I have been told they are urgently working on creating a summary of the bug
22:35:53 From phil | EOS Switzerland : the auditor is trying to join but cannot due to 200 users
22:35:54 From Josh Kauffman EOS Canada : Regarding: minutes to finalization. Let’s ask Dan when aBFT will be implemented. If it’s months away, Jem would you like to wait those months?
22:36:14 From Rohan - EOS Authority : absolutely ask Dan for his comment on RAM as expert witness. he might need all the facts and it should be 100% discussion on facts.
22:36:23 From ZhaoYu - EosLaoMao : local voting portal is necessary, we build one for it: https://github.com/EOSLaoMao/eos-local-voter
22:36:41 From ZhaoYu - EosLaoMao : Always keep your keys local
22:37:31 From Block Lord l EOSindia : we are building new voting solution
22:37:34 From winlin-EOSBIXIN : cool
22:37:40 From winlin-EOSBIXIN : print
22:37:42 From Jacky - JEDA : problem solved
22:37:51 From Block Lord l EOSindia : a simple easy to understand and use ui
22:38:43 From Douglas Horn | EOSAmericas : The solution would probably be a lot more acceptable to users if Dan issues this explanation.
22:38:46 From Mitch Sanders : while it's fresh in everyone mind let's get a vote
22:38:46 From Yasong “matt” Shi UnlimitedEOS : cool
22:39:00 From Mitch Sanders : while it's fresh in everyone mind let's get a vote. and move on from there...
22:39:02 From phil | EOS Switzerland : i disagree, I vote no to this issue
22:39:30 From phil | EOS Switzerland : one second I have a phone call
22:39:46 From Douglas Horn | EOSAmericas : I was against it before but I am less concerned now that Dan has weighed in.
22:39:49 From Mitch Sanders : while it's fresh in everyone mind let's get a vote
22:40:03 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Translation time?
22:40:11 From cupide EOS Pacific : translate ，plz
22:40:41 From Block Lord l EOSindia : WTF is that Chinese speaking
22:40:55 From Leo | EOSphere.io : rap god
22:41:00 From Alexandre Bourget EOS Canada : ----------------------------------------------------------
----------------------------------------------------------
----------------------------------------------------------
QUESTION: SHOULD WE "PRINT" 19K EOS, OR "WORK OUT" A SOLUTION TO HAVE 1B FLUSH BEFORE LAUNCH?
Please answer "PRINT" or "WORK OUT".
22:41:04 From Weifeng@EOS.LAWYER : let's do it, launch the eos main net
22:41:04 From Yves La Rose - EOS Nation : please be respectful
22:41:14 From phil | EOS Switzerland : my main concern is that, I dont think dan fully empathizes with the experience of the lay person. I think these things need to be as simple and dumbed down as possible, and as is- that is NOT the case
22:41:15 From James Sutherland - Cypherglass : PRINT
22:41:17 From Yasong “matt” Shi UnlimitedEOS : PRINT
22:41:17 From Sebastian Castro - EOS Argentina : Let’s print more tokens and we can create a worker proposal asking token holders if the like them to to burn this tokens (from the fund) or not.
22:41:22 From Greg | EOSsxsw : WORK OUT
22:41:23 From Aaron (Greymass) : If it becomes a point of contention, the elected block producers can retire the the amount to offset whatever extra was created. At that point, the actual stakeholders are deciding based on who they elect.
22:41:24 From Nate D - Aloha EOS : PRINT
22:41:26 From Craig@BlockSmith : print please
22:41:26 From Miłosz Eos Emerge Poland : PRINT
22:41:26 From dlarimer : Low Latency BFT is months away and will require test networks to validate
22:41:27 From Marc-Antoine Ross EOS Canada : PRINT
22:41:27 From Nathan (GenerEOS) : print
22:41:30 From Aaron (Greymass) : print
22:41:31 From Lars Ihler - Bitspace : WORK OUT
22:41:32 From Alexandre Bourget EOS Canada : PRINT
22:41:38 From Jorge@EOSMetal : PRINT
22:41:39 From Ross (EOSphere) : PRINT
22:41:39 From Jacky - JEDA : PRINT
22:41:40 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Work Out
22:41:41 From Patrick B - Aloha EOS : PRINT
22:41:43 From Sharif - EOS Dublin : PRINT
22:41:44 From Yves La Rose - EOS Nation : print
22:41:45 From crazybit@SuperONE.io : PRINT IT
22:41:46 From JoseT -eosMeso also at tulip want to look at chat : issue then burn
22:41:51 From Buddy Deck - EOS New York : print
22:41:52 From Ralf Weinand : print
22:41:53 From Weifeng@EOS.LAWYER : PRINT
22:41:53 From simon EOS Store : print
22:41:56 From Sebastian Castro - EOS Argentina : Print
22:42:00 From Swandoyo@EOS Cafe Calgary : print
22:42:01 From Douglas Horn | EOSAmericas : Print then burn
22:42:05 From Mitch Sanders : the architect says it's time to go.
22:42:12 From Celu - Blockgenic : print
22:42:15 From Ricardo-EOSBrazil : how many times we voted on that exact same question though?
22:42:15 From Block Lord l EOSindia : print
22:42:19 From Timothy Lewis - LibertyBlock : Work out. increased ram cost and extra bp rewards still exist.
22:42:20 From Jialin@EOS WTZ : PRINT
22:42:20 From Joshua Qiu@EOSeco : print
22:42:23 From Tulip conf : print
22:42:24 From santhosh - EOSNodeOne : print
22:42:24 From tmuskal @ LiquidEOS : print
22:42:25 From Alex - EOS SOCAL : print
22:42:25 From Gordo - HelloEOS : print
22:42:25 From Leo | EOSphere.io : can you repeat the question please
22:42:25 From Lars Ihler - Bitspace : work out
22:42:26 From kedar - LibertyBlock : print
22:42:28 From Issay Tseng@OracleChain : WORK OUT
22:42:28 From Mitch Sanders : print
22:42:29 From Sebastian Castro - EOS Argentina : Print
22:42:30 From Pascal | EOS Network : Print
22:42:30 From EOSWenzhou : print
22:42:31 From Pete @ Block Matrix : Work out
22:42:31 From wajid malik - Bitspace : print
22:42:33 From Eric - sw/eden : work out
22:42:36 From Dafeng EOS Asia : print
22:42:36 From Zachary Rogers : print
22:42:37 From Igor Lins e Silva - EOS Rio : work out
22:42:38 From nick- Eos.Fish : Work out
22:42:38 From Leeroy Jenkins : Work out
22:42:39 From guillaume@eostitan.com : work out
22:42:41 From Rob Konsdorf - EOS Detroit : Work out
22:42:42 From khosi - eosAfrica : work out
22:42:43 From EOS42 & EOS New York : print (EOS42)
22:42:43 From Yvonne@eoshenzhen : work out
22:42:44 From Tim | GenerEOS : print
22:42:44 From Benjamin Wang@EOShenzhen : work out
22:42:44 From Tim Ogilvie - Staked : print
22:42:46 From Jason-EOS Pacific : print
22:42:46 From david : print
22:42:46 From J.T. - EOS The World : Work Out
22:42:47 From Patrick Hajek eosarmy : print
22:42:47 From lemosn@EosLaoMao : print
22:42:47 From Kevin@EOS Galaxy : Print
22:42:47 From Jinma EOS Asia : print
22:42:48 From Bean - EOS Cannon : work out
22:42:50 From gustavomick-eosargentina : Print
22:42:51 From Ben SHEOS : work out
22:42:53 From skep EOSJRR : work out
22:42:54 From Edward - EOS Land : Print
22:42:55 From Bo - EOS Silicon Valley : print
22:42:56 From Mr Fox@EOS WTZ : print
22:42:57 From Albert-EosThu : print
22:42:58 From Weifeng@EOS.LAWYER : print
22:42:58 From heejae - EOSYS : print
22:43:00 From DS Lim - EOSeoul : Work out
22:43:02 From deadlock - EOSIO.SG : work out
22:43:05 From Leo | EOSphere.io : print
22:43:07 From MEET.ONE : work out.
22:43:08 From galaxy : work out
22:43:08 From Luis Fernando EOSMESOdotio : Print
22:43:11 From andrew - EOS JRR : work out
22:43:13 From ZhaoYu - EosLaoMao : print
22:43:14 From Ravi (BlockPro) : work out
22:43:21 From sherman eosreal : print
22:43:29 From robin@SuperONE.io : PRINT
22:43:30 From lochaiching-EOShenzhen : Work out
22:43:48 From Ricardo-EOSBrazil : work out
22:44:11 From Emily - shEOS : workout
22:44:12 From Rob - Worbli : print
22:45:12 From TrucNguyen : print
22:45:26 From Ross (EOSphere) : Marc.. I have no idea who Leo | Esophere.io is?
22:45:43 From Marek Eos Emerge Poland : print
22:45:55 From Kurt - BPAC : print
22:46:07 From Rohan - EOS Authority : print
22:46:09 From Leo | EOSphere.io : I'm new
22:46:14 From Thomas Cox (not a BP) : END OF VOTE FOR PRINT VS WORK OUT
22:46:17 From Alexandre Bourget EOS Canada : ------------------------------------------------------------------
------------------------------------------------------------------
------------------------------------------------------------------
22:46:42 From Thomas Cox (not a BP) : I'm counting now
22:48:10 From Lars Ihler - Bitspace : how do you know real/invalid votes, Thomas?
22:48:34 From Douglas Horn | EOSAmericas : If we recommend an interface, we share responsibility if people are hacked. Safer not to endorse anything for now.
22:48:39 From Block Lord l EOSindia : any exchanges admins are present here?
22:48:58 From Aaron (Greymass) : That’d be me
22:49:13 From Weifeng@EOS.LAWYER : huobi will vote on behalf of its users
22:49:18 From Timothy Lewis - LibertyBlock : git ?
22:49:24 From Timothy Lewis - LibertyBlock : Greymass?
22:49:34 From Aaron (Greymass) : https://github.com/greymass/eos-voter
22:51:41 From phil | EOS Switzerland : the reason ethereum is failing is because of slow speed in development and reaching consensus, I think sometimes we just have to trust in technology and directly reach out to what we seek in our future
22:52:32 From James Sutherland - Cypherglass : Quick auto count ... not perfect, but gives you an idea. I stripped the first 503 lines off the top of the chat before running.
22:52:33 From James Sutherland - Cypherglass : $ grep -i work meeting_saved_chat.txt | grep -c out
24
$ grep -ci "print^M" meeting_saved_chat.txt
70
22:52:40 From J.T. - EOS The World : So basically, the lay man won't vote.
22:52:54 From phil | EOS Switzerland : exactly
22:52:56 From phil | EOS Switzerland : that is a problem!
22:52:57 From J.T. - EOS The World : If it comes out that we can't recomend a portal.
22:53:00 From ZhaoYu - EosLaoMao : Would love some one to audit our local voter code: https://github.com/EOSLaoMao/eos-local-voter
22:53:17 From Alexandre Bourget EOS Canada : James, you need to dedupe BPs, remove those who didn't add their BP name to their name, and remove conflicting votes from the same BP (there were a few like that)
22:53:28 From Aaron (Greymass) : Just because the group as a whole cannot recommend a tool, doesn’t mean individual BPs or other individuals can’t recommend these options to others based on their experiences.
22:53:48 From Sharif - EOS Dublin : Auditing of voting portals will come with time and each individual BP can recommend , but as a Launch Group we can only recommend CLEOS
22:54:21 From Edward - EOS Land : 投票工具需由投票自己来决定
22:54:39 From Tulip conf : Tulip conf is a bunch of block producers
22:54:55 From Issay Tseng@OracleChain : can we use google sheets?
22:55:27 From Tulip conf : tulip conf is all split up now, single BP should be used for votes now
22:57:03 From Edward - EOS Land : 到现在为止，说是没有发现任何P1或P0问题
22:58:30 From Bruce | Block Foundations Australia : PRINT
22:58:51 From Bruce | Block Foundations Australia : Ah gosh I have terrible lag. Sorry.. guess I missed that vote
22:59:01 From Weifeng@EOS.LAWYER : GO
22:59:13 From Block Lord l EOSindia : Go
22:59:14 From phil | EOS Switzerland : voting does not start until officially started
22:59:22 From Sebastian Castro - EOS Argentina : GO!
22:59:28 From Alexandre Bourget EOS Canada : -------------------------------------------
-------------------------------------------
-------------------------------------------
QUESTION: SHOULD WE "LAUNCH" AT 1300 UTC FRIDAY ?
Otherwise, say "NO"
22:59:35 From guillaume@eostitan.com : NO
22:59:44 From phil | EOS Switzerland : this is confusing
22:59:48 From phil | EOS Switzerland : i thought we were doing go or no go?
22:59:49 From Block Lord l EOSindia : yeah
22:59:53 From Weifeng@EOS.LAWYER : GO
22:59:54 From fun@eosmedi : Go!
22:59:56 From heejae - EOSYS : GO
22:59:57 From guillaume@eostitan.com : NO GO
22:59:58 From zhangzc : go
22:59:59 From Sebastian Castro - EOS Argentina : GO
22:59:59 From Nate D - Aloha EOS : GO
22:59:59 From Buddy Deck - EOS New York : go
23:00:00 From Aaron (Greymass) : go
23:00:00 From Ross (EOSphere) : GO!
23:00:00 From Yasong “matt” Shi UnlimitedEOS : GO！！
23:00:00 From wajid malik - Bitspace : Go
23:00:00 From Norsefire : go
23:00:00 From zformular@EOSBepal : Go
23:00:01 From Tulip conf : eos nation - GO
23:00:01 From Tim Ogilvie - Staked : GO
23:00:01 From Edgar@EOS Costa Rica : GO
23:00:01 From Swandoyo@EOS Cafe Calgary : GO!
23:00:01 From Miłosz Eos Emerge Poland : go
23:00:01 From simon EOS Store : GO
23:00:02 From Rob - Worbli : go
23:00:02 From Marc-Antoine Ross EOS Canada : GO
23:00:02 From phil | EOS Switzerland : NO GO
23:00:02 From zhengyu@infinitystones - EOS Danhua : go
23:00:02 From winlin-EOSBIXIN : go
23:00:02 From ZhaoYu - EosLaoMao : go
23:00:03 From Alexandre Bourget EOS Canada : -------------------------------------------
-------------------------------------------
-------------------------------------------
QUESTION: SHOULD WE "GO", or "NO GO" ?
23:00:03 From Ralf @ GenerEOS : go
23:00:03 From kedar - LibertyBlock : GO
23:00:03 From Jorge@EOSMetal : go
23:00:03 From robin@SuperONE.io : GO
23:00:03 From Rob Konsdorf - EOS Detroit : go
23:00:03 From Greg | EOSsxsw : NO GO
23:00:04 From John | discoverEOS.space : GO OR NO GO
23:00:04 From Jacky - JEDA : GOOO
23:00:04 From nick- Eos.Fish : Go
23:00:05 From Jialin@EOS WTZ : GO
23:00:06 From Gordo - HelloEOS : go
23:00:06 From Joshua Qiu@EOSeco : GO
23:00:06 From Hank@EOS Palliums : go
23:00:07 From aiguo : go
23:00:08 From Norsefire : go
23:00:08 From Alex - EOS SOCAL : Go
23:00:11 From Block Lord l EOSindia : Go
23:00:11 From Weifeng@EOS.LAWYER : GO
23:00:12 From EOSWenzhou : go
23:00:12 From Tulip conf : blockeos.io - GO
23:00:17 From Marshall - SaltBlock : Go
23:00:18 From Lievin - EOSYS : Go
23:00:18 From phil | EOS Switzerland : people are typing many times
23:00:18 From Yves La Rose - EOS Nation : go
23:00:18 From Jason-EOS Pacific : go
23:00:20 From Craig@BlockSmith : go
23:00:20 From Rohan - EOS Authority : Go
23:00:20 From py@eos.cybex : Go
23:00:23 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : NO GO
23:00:26 From Marek Eos Emerge Poland : GO
23:00:26 From James Sutherland - Cypherglass : Go
23:00:29 From Celu - Blockgenic : go
23:00:31 From EOS42 & EOS New York : Go (EOS42)
23:00:33 From david : GO
23:00:33 From phil | EOS Switzerland : i am voting no go
23:00:36 From Ralf @ GenerEOS : go
23:00:39 From phil | EOS Switzerland : eos swiss - no go
23:00:39 From Tulip conf : eos nation - GO
23:00:47 From Albert-EosThu : go
23:00:51 From Norsefire EOS Singapore : Go
23:01:00 From Weifeng@EOS.LAWYER : EOS LAWYER - GO
23:01:04 From Pascal | EOS Network : GO
23:01:06 From Sharif - EOS Dublin : Go
23:01:06 From Douglas Horn | EOSAmericas : No go
23:01:15 From Luis Fernando EOSMESOdotio : No go
23:01:16 From Yvonne@eoshenzhen : NO GO
23:01:18 From cupide EOS Pacific : 北京时间今天周五晚上9点主网是否上线？go 上线，no go 不上线。
23:01:20 From Eric - sw/eden : no go
23:01:21 From deadlock - EOSIO.SG : no go
23:01:24 From Timothy Lewis - LibertyBlock : no go
23:01:27 From lochaiching-EOShenzhen : no go
23:01:28 From galaxy : no go
23:01:28 From tmuskal @ LiquidEOS : no go
23:01:29 From phil | EOS Switzerland : I think the risk of a p1 bug is too high
23:01:30 From J.T. - EOS The World : no go
23:01:34 From lemosn@EosLaoMao : go
23:01:46 From Igor Lins e Silva - EOS Rio : no go
23:01:48 From Issay Tseng@OracleChain : NO GO（OracleChain）
23:01:52 From Ben SHEOS : no go
23:01:53 From BlockBeats-China : 9 pm is totally a good time for Chinese.
23:01:56 From phil | EOS Switzerland : we are just speculating that there is not a p1 bug with the shadow transaction propagation based on dan larimer?
23:01:57 From Peter Bue EOS Americas : 12 hours? Did no time pass during this meeting?
23:01:59 From phil | EOS Switzerland : its ludicrous
23:02:00 From Edward - EOS Land : 现在要投票，北京时间周五晚上9点是否启用主网
23:02:04 From Ricardo-EOSBrazil : no go
23:02:05 From DS Lim - EOSeoul : GO
23:02:08 From phil | EOS Switzerland : its a clear no go
23:02:12 From Ravi (BlockPro) : NO GO
23:02:18 From Block Lord l EOSindia : yeah no go
23:02:19 From Roman CryptoLions : no go
23:02:19 From fun@eosmedi : GO
23:02:31 From Dafeng EOS Asia : Go
23:02:48 From Patrick Hajek eosarmy : go
23:02:49 From Norsefire : Guys - just something to highlight: this is effectively a 14 billion dollar network, and we're leaving launch down to a Twitch style SPAM ME DADDY WE'RE VOTING NOW
23:02:54 From Bo - eos silicon valley : Go
23:02:54 From EOS42 & EOS New York : There are many voting that are not block producers.
23:02:54 From Pete @ Block Matrix : no go
23:02:56 From Craig@BlockSmith : phil | EOS Switzerland has voted 4 times at least
23:03:01 From Emily - shEOS : No go
23:03:05 From JoseT -eosMeso also at tulip want to look at chat : first finish print or work out issue
23:03:13 From zhangzc : go
23:03:14 From phil | EOS Switzerland : it was one vote meant to be
23:03:28 From Weifeng@EOS.LAWYER : definitely go
23:03:37 From Nathan (GenerEOS) : go
23:03:39 From tokenpocket EOSUNION : GO
23:03:42 From kai jing- no bp : another issue, 1 vote per bp, i think will ne better
23:03:54 From Weifeng@EOS.LAWYER : because we vote here, and real voters will vote on blockchain, meet 15% is real go
23:03:55 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Presumably, a ‘go’ decision means we need to get 1.0.2, build with new constitution, validate paused chain after resign. Should be done before 1300.
23:04:07 From Hugo - EOS SV : No go
23:04:08 From Alex : nobody is BPs until it’s voted by community
23:04:09 From wudi : Why No go from Chinese？
23:04:10 From Block Lord l EOSindia : let's solve print issue first
23:04:16 From phil | EOS Switzerland : the question was clear and I think there is definitely not 2:1 in favor
23:04:27 From Ravi (BlockPro) : 24 hrs more is not a big issue
23:04:32 From Jason-EOS Pacific : go
23:04:59 From Weifeng@EOS.LAWYER : there is no obvious reason for "NO GO", so we should GO GO GO
23:05:01 From phil | EOS Switzerland : can we do a revote
23:05:02 From Mike Seiler : Will you stay or will you go
23:05:09 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : ABP needs to be selected, and do all those jobs.
23:05:16 From david : should do a re-vote
23:05:22 From Yasong “matt” Shi UnlimitedEOS : Lets do a revote
23:05:25 From david : BP only, of course
23:05:26 From phil | EOS Switzerland : one vote per person
23:05:27 From Greg | EOSsxsw : yes. revote
23:05:29 From phil | EOS Switzerland : BP only
23:05:31 From Greg | EOSsxsw : too much confusion
23:05:39 From Mike Seiler : How to get consensus
23:05:40 From andrew - EOS JRR : go
23:05:44 From Aaron (Greymass) : Not everyone has to be live at minute 1.
23:05:44 From Block Lord l EOSindia : yeah revote
23:06:25 From Bruce | Block Foundations Australia : make it LAUNCH vs GO. Otherwise your grep count may fail
23:06:29 From Lievin - EOSYS : I think for GoNoGO vote we should say “Yes - BP Name”
23:06:31 From Yasong “matt” Shi UnlimitedEOS : Lets do revote
23:06:31 From Edward - EOS Land : 1.0.2？
23:06:33 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Wait for 1.0.2
23:06:49 From Weifeng@EOS.LAWYER : software update so frequently, we dont vote version
23:06:57 From Rohan - EOS Authority : why wait. Dan said they are not blockers.
23:07:00 From phil | EOS Switzerland : -------------------------------------------
-------------------------------------------
-------------------------------------------
QUESTION: SHOULD WE "LAUNCH" AT 1300 UTC FRIDAY ? VOTE: LAUNCH for yes, GO for good to go, but not that time NO for NO LAUNCH
23:07:04 From Weifeng@EOS.LAWYER : let's just get show started.
23:07:17 From nick- Eos.Fish : Leave the chat for votes this time. Dont share your opinion 12 times
23:07:19 From Aaron (Greymass) : This isn’t a HF change, each producer can upgrade to 1.0.2 at their leisure.
23:07:24 From Ricardo-EOSBrazil : we voted already. are we keep revoting things? this is really weird
23:07:33 From Ricardo-EOSBrazil : we voted PRINT x WORKOUT at least 4 times
23:07:38 From Ricardo-EOSBrazil : this is nonsense
23:07:58 From Mike Seiler : This is literally The Byzantine Generals Problem
23:08:09 From Sharif - EOS Dublin : I suggest we re-vote based on available release 1.0.1
23:08:19 From Aaron (Greymass) : It’s almost like we need a consensus engine with voting running to solve it.
23:08:23 From Peter Bue EOS Americas : With a deadline that has been known for so long. There should have been a more secure and controlled way to vote on these proposals.
23:08:23 From Greg | EOSsxsw : we should write an ethereum smart contract to record our votes
23:08:28 From Peter Bue EOS Americas : ^^^^^
23:08:30 From Peter Bue EOS Americas : Yes
23:08:34 From phil | EOS Switzerland : +1
23:08:39 From Block Lord l EOSindia : yes
23:08:43 From phil | EOS Switzerland : I think using ethereum would be good idea
23:08:43 From khosi - eosAfrica :
Why not vote on a Saturday 13:00 launch then?
23:08:52 From Jinma EOS Asia : 达峰你声音有点低。
23:09:08 From nick- Eos.Fish : Because we need time to prepare. Voting at the next meeting would delay another 12 hours
23:09:19 From Douglas Horn | EOSAmericas : +1 to Peter Bue
23:09:24 From Craig@BlockSmith : that dude's mike is super loud! wow
23:09:25 From Mitch Sanders : surprised that some of the smartest developers in the world are on this call and relying on chat votes with trust to vote on a trustless system. makes no sense.
23:09:42 From Lars Ihler - Bitspace : hahah
23:09:47 From Ricardo-EOSBrazil : guys. we waited 1 year. 1 week is nothing...
23:09:50 From david : I am not a BP, but come on people, promises were made about a vote.
23:09:55 From dlarimer : The voting process was suppose to be people connecting to a network and voting their stake
23:09:57 From phil | EOS Switzerland : Mitch, i said once and I said it twice, that we NEED more consistency by dan larimer if we want EOS to succeed
23:10:10 From Caleb | EOS-Singapore User's Group : I think we're ready to go
23:10:13 From Caleb | EOS-Singapore User's Group : It's been long enough
23:10:25 From Weifeng@EOS.LAWYER : YES. let's go.
23:10:36 From Mitch Sanders : surprised that some of the smartest developers in the world are on this call and relying on chat votes with trust to vote on a trustless system. makes no sense.
23:10:38 From wudi : This guys just said must people form china says GO
23:10:58 From phil | EOS Switzerland : Rules: 1 vote per person, Block producers only! If you are not a block producer, put a $ next to your vote!
23:11:03 From nick- Eos.Fish : Final vote. Please don’t clutter the chat this time
23:11:07 From phil | EOS Switzerland : example, GO vs Go$
23:11:17 From Mitch Sanders : launch vs go.
23:11:19 From nick- Eos.Fish : Or just dont vote
23:11:21 From Mitch Sanders : make it simple
23:11:37 From John | discoverEOS.space : can we implement some kind of EOS voting wheel contract
23:12:01 From Mitch Sanders : or do it like Congress.
23:12:02 From Ravi (BlockPro) : mITCH it is not launch vs go.. it is go vs no go.. what you say confuses people
23:12:14 From Mitch Sanders : ask each BP individually and note in a spreadsheet
23:12:32 From Ravi (BlockPro) : GO or No Go based on 1.0.1 to clarify
23:12:33 From Caleb | EOS-Singapore User's Group : Hey guys I created this poll - you can only access it if you have the direct link
23:12:38 From Caleb | EOS-Singapore User's Group : I suggest we use this to make things easier than chat
23:12:38 From Caleb | EOS-Singapore User's Group : https://strawpoll.com/aks63ckz
23:12:49 From Angelia@EosStore : 兼容性问题，应该是可以兼容的吧
23:12:53 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : I think https://github.com/EOSIO/eos/issues/3917 is a P1, and is solved only by patch included in 1.0.2
23:12:55 From phil | EOS Switzerland : -----_---
-----
----
FIRST - We need to declare who IS a BP and who IS NOT- if you are a BP Please say YES to this message!
23:12:58 From wudi : yes
23:13:00 From phil | EOS Switzerland : YES
23:13:06 From Nathan (GenerEOS) : yes
23:13:06 From Ricardo-EOSBrazil : troll
23:13:08 From Ralf @ GenerEOS : Yes
23:13:10 From Weifeng@EOS.LAWYER : YES
23:13:11 From Tim Ogilvie - Staked : Yes
23:13:13 From sherman eosreal : yes
23:13:13 From Yves La Rose - EOS Nation : Yes
23:13:14 From Edgar@EOS Costa Rica : yes
23:13:15 From Lars Ihler - Bitspace : yes
23:13:15 From Caleb | EOS-Singapore User's Group : yes
23:13:15 From Celu - Blockgenic : yes
23:13:16 From John | discoverEOS.space : did we voted yet
23:13:17 From Block Lord l EOSindia : yes
23:13:22 From Timothy Lewis : yes
23:13:23 From Joshua Qiu@EOSeco : GO 1300 UTC （EOSeco）
23:13:23 From Aaron (Greymass) : yes
23:13:24 From Igor Lins e Silva - EOS Rio : yes
23:13:26 From wajid malik - Bitspace : yes
23:13:26 From Sharif - EOS Dublin : Yes
23:13:26 From Rob - Worbli : go
23:13:27 From zformular@EOSBepal : yes
23:13:27 From Mr Fox@EOS WTZ : yes
23:13:29 From Sebastian Castro - EOS Argentina : Yes, GO!
23:13:31 From Angelia@EosStore : go
23:13:32 From DS Lim - EOSeoul : yes
23:13:33 From Swandoyo@EOS Cafe Calgary : Yes
23:13:33 From Yasong “matt” Shi UnlimitedEOS : YES
23:13:35 From Peter Bue EOS Americas : That doesn’t filter out non-bps
23:13:37 From Adrian - SaltBlock : +1 — this twitch style voting is shameful.
23:13:40 From guillaume@eostitan.com : yes
23:13:41 From Rohan - EOS Authority : Yes. EOS Authority.
23:13:42 From Greg | EOSsxsw : yes
23:13:44 From Timothy Lewis : we are not voting on go no go
23:13:44 From Tulip conf : yes - eos nation , blockeos.io
23:13:49 From Mitch Sanders : yes ross
23:13:49 From Douglas Horn | EOSAmericas : Good idea
23:13:51 From Timothy Lewis : yes means your are a BP
23:13:51 From Yasong “matt” Shi UnlimitedEOS : I agreed
23:13:54 From nick- Eos.Fish : I like that approach
23:13:56 From Caleb | EOS-Singapore User's Group : Strawpoll Idea: https://strawpoll.com/aks63ckz
23:13:57 From EOS42 & EOS New York : Yes (EOS42)
23:13:58 From wudi : Just let the ABPC to vote
23:14:01 From phil | EOS Switzerland : YES = BP
23:14:09 From Issay Tseng@OracleChain : YES
23:14:16 From John | discoverEOS.space : yes
23:14:20 From phil | EOS Switzerland : alright, so we know who is BP now
23:14:23 From phil | EOS Switzerland : now we can VOTE
23:14:24 From Block Lord l EOSindia : straw poll can be manipulated using vpn
23:14:28 From andrew - EOS JRR : yes
23:14:39 From zhangzc : yes
23:14:42 From Peter Bue EOS Americas : Straw poll also won’t filter out non BP votes.
23:14:48 From gustavomick-eosargentina : This is important enough to create a new zoom link and share it thru voting channel, and do voting again.
23:14:56 From phil | EOS Switzerland : We have identified who is a BP by who said 'yes'
23:15:00 From phil | EOS Switzerland : those are the ONLY votes that should be counted
23:15:02 From Mike Seiler : how can we trust that vote count lmao
23:15:12 From Yasong “matt” Shi UnlimitedEOS : I agreed we do a video vote, raise hand say go no go
23:15:24 From nick- Eos.Fish : Lots of BP’s including myself havetn been able to get into the voting channel
23:15:34 From Douglas Horn | EOSAmericas : We should vote by presenting our official BPC name followed by a clear vote.
23:15:36 From Dean Free Space : roll call vote. live sever on validated chain only.
23:15:41 From Issay Tseng@OracleChain : use google sheets, sign with you BP name
23:15:45 From phil | EOS Switzerland : telegram has a phishing problem
23:15:50 From phil | EOS Switzerland : lots of scammers
23:15:52 From david : For crying out loud we wasted more time talking about how to vote than voting. Just have very BP video answer
23:15:52 From phil | EOS Switzerland : we should not use it
23:15:59 From Aaron (Greymass) : I’m not in the validation channel.
23:16:01 From Chitty - EOS Argentina : Validation channel seems safer
23:16:04 From Tim Ogilvie - Staked : Validation channel excludes lots of BPs
23:16:05 From Marek Eos Emerge Poland : Its a good idea
23:16:07 From Peter Bue EOS Americas : Validation Channel is probably the best venue for this.
23:16:09 From gustavomick-eosargentina : Yeah, share a new link thru validation channel.
23:16:09 From Marek Eos Emerge Poland : telegram
23:16:12 From Caleb | EOS-Singapore User's Group : I agree, we need to make sure that only BP's vote
23:16:14 From Yasong “matt” Shi UnlimitedEOS : For crying out loud we wasted more time talking about how to vote than voting. Just have very BP video answer
23:16:15 From Edgar@EOS Costa Rica : We are not in the validation channel. we need link pls
23:16:15 From nick- Eos.Fish : Or not letting people in who requested over the last 2 days. I cannot get into the validation channel
23:16:21 From Peter Bue EOS Americas : Dont share the link in here!
23:17:11 From Douglas Horn | EOSAmericas : Could we vote by adding “go” or No Go” to our bp_info.json file and then pointing to that?
23:17:33 From phil | EOS Switzerland : what?
23:17:37 From phil | EOS Switzerland : are you serious dan?
23:17:37 From Douglas Horn | EOSAmericas : Each BP should have a single bp_info.json file on their web site.
23:17:42 From phil | EOS Switzerland : you just want to find people who launch?
23:18:05 From crazybit@SuperONE.io : bp.json or bp_info.json
23:18:36 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : bp.json
23:18:45 From Ben SHEOS : BP_JSON can be gamed as well
23:18:45 From crazybit@SuperONE.io : It is bp.json refer to https://github.com/EOSPortal/bp-info-standard/
23:19:24 From david : How many GO votes from BPs are required for a go? David Moss can ping them alphabetically and stop when we either hit that number, or when we run out of BPs. Problem solved. Much faster.
23:20:32 From Edgar@EOS Costa Rica : not all BP candidates are on that validation chat
23:20:33 From nick- Eos.Fish : Me
23:20:34 From Aaron (Greymass) : I am not.
23:20:40 From Tim Ogilvie - Staked : I’m not https://staked.us/bp_info.json
23:20:41 From Edgar@EOS Costa Rica : we are not
23:20:43 From phil | EOS Switzerland : I am not in the validation channnel
23:20:44 From david : I am not a BP, but i still want to watch
23:20:45 From tmuskal @ LiquidEOS : we am not
23:20:53 From Block Lord l EOSindia : I m not
23:20:54 From nick- Eos.Fish : Nobody from eos.fish has been able to get into the validation channel
23:21:07 From Douglas Horn | EOSAmericas : Yes to ordering room service.
23:21:08 From phil | EOS Switzerland : yeah, they have been keeping it too close knit
23:21:14 From phil | EOS Switzerland : it is unfair to other block producers
23:21:28 From david : This needs to be out in the open.
23:21:40 From Josh Kauffman EOS Canada : Phil from EOS Switzerland. No one has heard of your BP. Please send a link to confirm you are an actual BP
23:21:49 From phil | EOS Switzerland : http://www.eosbros.eu/ its swiss based
23:21:49 From Edgar@EOS Costa Rica : all block producers candidates should be able to vote on this. let’s do the vote here
23:21:57 From Dennis : why can't a simple survey money survey be sent to all BP's and vote open for 5mins...
23:21:59 From phil | EOS Switzerland : sorry
23:22:02 From phil | EOS Switzerland : i can change if you want
23:22:59 From Greg | EOSsxsw : BPs who want to GO should GO
23:23:03 From phil | EOS Switzerland : we have some other partners in the area that are not officially eosbros
23:23:06 From phil | EOS Switzerland : that is why I just say switzerland
23:23:13 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : Want to launch with 1.0.1 and known P1?
23:23:35 From Peter Bue EOS Americas : I don’t think anyone is voting in telegram.
23:23:52 From phil | EOS Switzerland : can someone private message me the telegram
23:24:38 From Dennis : why not 10.02 then 1.0.3 etc?
23:24:43 From Mitch Sanders : But what if there is bugs in 1.0.2? another 48 hours?
23:24:44 From Ravi (BlockPro) : 1.0.2 and transaction verification has to be accurate
23:24:50 From Mitch Sanders : 80/20 rule
23:25:01 From Edgar@EOS Costa Rica to Josh Kauffman EOS Canada (Privately) : hi from EOS Costa Rica , can I pls have the telegram validation invite please
23:25:07 From Eric - sw/eden : Ran out of batteries on my headphones.
23:25:14 From Eric - sw/eden : Can listen but not speak.
23:25:15 From jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet : But, select ABP asap to let him get started.
23:25:16 From Mitch Sanders : perfection is the enemy of progression
23:25:21 From tmuskal @ LiquidEOS : people will want to vote asap and they will not have verified easy to use tools yet. maybe we should define a soft launch. allowing transactions but not inviting people to vote yet.
23:26:56 From Aaron (Greymass) : Someone invite me - @jestagram
23:27:34 From Aaron (Greymass) : You can upgrade to 1.0.2 at will
23:27:50 From Aaron (Greymass) : You don’t need approvals for 1.0.2
23:27:55 From Aaron (Greymass) : This isn’t a hardfork
23:28:03 From phil | eosbros : this seems very centralized
23:28:19 From Rob Konsdorf - EOS Detroit : Jesta - I can’t add you to the telegram channel due to your privacy settings.
23:28:21 From Weifeng@EOS.LAWYER : invite me @weifeng
23:28:27 From Rohan - EOS Authority : exactly. don’t worry about approvals. this is not P1 or P0
23:29:00 From Josh Kauffman EOS Canada : EOS Lawyer seems to be a dApp and not a BP
23:29:00 From Mitch Sanders : votes of no go based on 1.0.2 which is a feature enhancement should be voided.
23:29:01 From zformular@EOSBepal : Someone invite me- EOS Bepal(@Bepal_admin)
23:29:02 From John | discoverEOS.space : did we voted already
23:29:11 From Douglas Horn | EOSAmericas : Our no-go vote was based on the concern that there has been no testing to confirm that 3918 is actually as Dan described it. I want to see some simple test protocol proposed to recreate the issue on a local bp and confirm that it is not in fact being propagated across the network.
23:29:19 From Aaron (Greymass) : Thanks, try again Rob
23:29:26 From Ben SHEOS : everyone say happy birthday to Kyle
23:29:29 From Angelia@EosStore : 并不影响
23:29:32 From phil | eosbros : I agree, I am the same mentality Douglas
23:29:55 From Mathieu - EOS Canada : On another note, on the Print / Work Out vote, I got (after cleaning the data): 55 Print, 31 work out
23:30:04 From Douglas Horn | EOSAmericas : It is a good explanation and I don’ tdoubt it, but I want to test it first. I think untested concerns are more important than an additional 12 hours of waiting.
23:30:16 From Leeroy Jenkins : Printing tokens on Day 1 will be a PR nightmare
23:30:32 From phil | eosbros : zoom crashing for anyone else?
23:30:50 From Rohan - EOS Authority : zoom fine
23:30:51 From david : Delaying launch for something that is merely inconvenient will be a bigger PR
23:32:14 From Ben SHEOS : great idea
23:32:24 From Douglas Horn | EOSAmericas : 9.5 hours at this point
23:32:35 From Douglas Horn | EOSAmericas : Could be 2 hours by the time the call is over
23:32:39 From Weifeng@EOS.LAWYER : minor version doens't matter
23:32:40 From Aaron (Greymass) : I am
23:32:44 From Craig@BlockSmith : YES FRUSTRATED
23:33:04 From James Sutherland - Cypherglass : MY COUNT
38 - go
27 - no-go
23:33:32 From Marek Eos Emerge Poland : Yes the no go has not much merit at this point
23:33:35 From Greg | EOSsxsw : We should fork if we need to. Those of us ready to GO should GO
23:33:41 From Dennis : if we're waiting for perfection, it doesn't exist. The no go arguments are fractured and unclear.
23:33:42 From Douglas Horn | EOSAmericas : Wait, we decided to vote here and decide based on the outcome of the vote. If it’s just waiting for the first 21 block producers, then that’s very different.
23:34:19 From Mitch Sanders : On another note, on the Print / Work Out vote, I got (after cleaning the data): 55 Print, 31 work out
23:34:22 From Weifeng@EOS.LAWYER : I am with david
23:34:25 From Mitch Sanders : MY COUNT
38 - go
27 - no-go
23:34:35 From phil | eosbros : yeah you cant change the rule - I just want more specific evidence that it will act the way it is speculated instead of, well simply speculation.
23:34:37 From Leeroy Jenkins : Doesn’t matter reason for vote, regardless of pick.
23:34:41 From Luis Fernando EOSMESOdotio : I don't think we have decided about the new eos print, and where pushing for a Go?
23:35:01 From Douglas Horn | EOSAmericas : We are ready to go, but we have all been asked to render an opinion. People are doing that.
23:35:05 From Rohan - EOS Authority : what about adding in the Chinese BPs
23:35:11 From Rohan - EOS Authority : votes
23:35:18 From Weifeng@EOS.LAWYER : just go, the whole community is waiting, and there is no big reason for "no go", let's go.
23:35:25 From Ravi (BlockPro) : Link for EOS Validation channel for those BPs not there yet
23:35:31 From david : the Chinese seemed to vote in a block, highly unusual,
23:35:45 From david : translation issue??
23:35:52 From Block Lord l EOSindia : they voted after translation
23:35:58 From tmuskal @ LiquidEOS : someone invite me please to validation group. @tmuskal (LiquidEOS from Bancor)
23:36:03 From Leeroy Jenkins : The reasoning for someone’s vote is irrelevant. We took a vote. Use the numbers.
23:36:18 From Caleb | EOS-Singapore User's Group : https://www.eosio.sg/
@CalebEOSSignapore , not on the telegram yet.
23:37:16 From EOSWenzhou : can somebody invite me,@superbigfu,we are eoswenzhou
23:37:20 From deadlock - EOSIO.SG : EOS Singpoare is not EOSIO.SG
23:37:20 From Mitch Sanders : waiting for 1.0.2 should be void
23:37:38 From phil | eosbros : i dont understand how the voting is valid when they are not allowing all BP's in the telegram
23:37:39 From Weifeng@EOS.LAWYER : no point to wait new version
23:37:48 From Caleb | EOS-Singapore User's Group : Sorry, misspelled my username. It's @CalebEOSSingapore
23:38:09 From Tim Ogilvie - Staked : We are here. Let us in
23:38:12 From Alexandre Bourget EOS Canada : https://abourget.keybase.pub/votetallysum.txt is my sum of first votes.
23:38:16 From Tim Ogilvie - Staked : Been here every meeting
23:38:24 From Tim Ogilvie - Staked : Can’t get into the Validator channel
23:38:36 From Douglas Horn | EOSAmericas : I was referring to ticket #3918, which I believe no one has verified and tested.
23:39:05 From Brent @ SaltBlock : Yeesh guys, vote seems to be in, right? Why draw this out with more rhetoric.
23:40:21 From Aaron (Greymass) : #3918 happens in DPoS chains - which is what Dan was trying to explain. It’s not something that’s magically going to be fixed unless you want to wait a while.
23:40:22 From Dennis : go
23:40:22 From Brent @ SaltBlock : Why refer to the firs vote? Just confusing things.
23:40:28 From Greg | EOSsxsw : we’ve spent too long catering to consensus. those who are ready should GO
23:40:38 From Weifeng@EOS.LAWYER : launch
23:40:44 From Ben SHEOS : the first vote we did was in this chat
23:40:49 From Weifeng@EOS.LAWYER : just launch, please
23:40:50 From Ben SHEOS : the second was in validation
23:40:53 From phil | eosbros : if you launch despite objection, then you are already creating a split in the community
23:41:06 From phil | eosbros : I dont think we should be creating factions this early
23:41:08 From Leeroy Jenkins : If we’re all in an agreement on the process, then the vote should be rule.
23:41:13 From Dennis : 2/3 +1 was reached in the first vote
23:41:14 From nick- Eos.Fish : What was the point in the last days worth of meetings if we are going to abandon the last 2/3 +1?
23:41:46 From Douglas Horn | EOSAmericas : ^^^^ agreee
23:41:48 From Leeroy Jenkins : The vote was no go. All the reason to not go. Why is this so difficult?
23:41:53 From Patrick Hajek eosarmy : I can understand why people are upset yet lets accept the vote and move on.
23:41:57 From aiguo-unlimitedeos : It's not fair that validation rejects a lot of real BPS
23:42:15 From phil | eosbros : we must follow the agreed on rules or else all integrity is ruined
23:42:22 From Yasong “matt” Shi UnlimitedEOS : So for now, The validation channel has keep some launch participation outside the vote process. And those has been working really hard for the launch process.
23:42:22 From david : But there is NO SPECIFIC P0 or P1. It is subjective, that this is a no-go.
23:42:26 From Douglas Horn | EOSAmericas : Can we improve the voting process?
23:42:26 From nick- Eos.Fish : Just because you don’t like the outcome doesnt mean you should just go off and start on your own without the rest
23:42:32 From phil | eosbros : +1
23:42:39 From david : What are the P0 and P1 bugs??— NOne
23:42:40 From Eric - sw/eden : We need a real tool to vote.
With stated questions that everyone clearly understand.
23:43:05 From Lievin - EOSYS : So the main issue is that
23:43:06 From nick- Eos.Fish : I voted Yes and am willing to respect the results of the vote
23:43:14 From zformular@EOSBepal : how about google doc to collection?
23:43:42 From phil | eosbros : if #3918 was tested successfully i would consider changing my vote
23:43:48 From aiguo-unlimitedeos : agreed, we need a real vote tool to allow all the bps join in
23:43:52 From Weifeng@EOS.LAWYER : that's right question. How to "GO"?
23:43:55 From Caleb | EOS-Singapore User's Group : If the following were true, I would change my vote to yes: If someone would add me to the telegram so I can actually cast my vote.
@CalebEOSSingapore
https://www.eosio.sg/
23:44:10 From Douglas Horn | EOSAmericas : If 3918 were tested and verified to be a local issue I would change my vote from “no-go” to “go”.
23:44:21 From Sharif - EOS Dublin : If the following were true I would change my vote to yes ; ABP appointed , 1.0.2 available
23:44:23 From deadlock - EOSIO.SG : why celeb has EOSIO.SG website under the name
23:44:28 From Weifeng@EOS.LAWYER : set conditions of "NO GO"
23:44:53 From Weifeng@EOS.LAWYER : why "NO GO", I want more clear answers
23:44:58 From Ravi (BlockPro) : Want 1.0.2 and verification of transaction transfer be fixed
23:45:17 From Leeroy Jenkins : “Block Producer Candidates met again at 01:00 to discuss the status of chain validation and the issues surrounding them and to conduct a go or no-go vote to launch the chain 12 hours later. The vote was a no-go.
BPCs are working hard and around the clock to make sure we have a successful launch. I addition a team of volunteers are gathering information to perform an audit to present recommendations for safe voting options for Token Holders.
“
23:45:19 From Mitch Sanders : https://abourget.keybase.pub/votetallysum.txt
23:45:24 From Mitch Sanders : seems like a go to me
23:45:26 From phil | eosbros : yes, we should also clarify the whole korean audit thing that was only briefly touched on yesterday
23:45:30 From phil | eosbros : they claimed it was a p1
23:45:31 From Mitch Sanders : 71 to 21
23:45:35 From phil | eosbros : but everyone just brushed it by
23:46:06 From jem proxy BP2 EOSPH hkeos eoskh Acro Tribes eosviet : Issue 3917 is a big usability problem, it is supposed to be fixed in 1.0.2
23:46:23 From Weifeng@EOS.LAWYER : oraclechain want to use newer version
23:46:27 From heejae - EOSYS : phil: Who is the Korean audit you contact? I am Korean and I never heard of Korean audits existing.
23:46:44 From Josh Kauffman EOS Canada : Phil from EOS BROS, if you have an issue to raise with this audit, please raise it. You were given the floor but then said you were on a phone call and didn’t explain.
23:47:02 From Buddy Deck - EOS New York : phil has changed his name. he seems to be trolling
23:47:02 From Weifeng@EOS.LAWYER : eos shenzhen dropped
23:47:09 From heejae - EOSYS : It looks like a FUD
23:47:12 From deadlock - EOSIO.SG : If the following were true, I would change my vote to yes: RAM solution is clear, 1.0.2 is available, ABP is appointed
23:47:28 From jem proxy BP2 EOSPH hkeos eoskh Acro Tribes eosviet : Agree with deadlock
23:47:31 From Weifeng@EOS.LAWYER : lochaiching is from eos shenzhen
23:47:47 From Yvonne@eoshenzhen : Print的钱 和安全性不够
23:48:16 From Leeroy Jenkins : Printing is a terrible idea on Day 1
23:48:26 From phil | eosbros : because they kicked me i think cause they claimed that my BP didnt exist ( i didnt know I needed the specific name, I thought location was okay). This was the agency that did the audit https://www.kisa.or.kr/main.jsp
23:48:37 From Lars Ihler - Bitspace : reasons for go or no-go is irrelevant.
23:48:54 From Ravi (BlockPro) : If you print more who is there to verify.. other than one ABP?
23:49:00 From Aaron (Greymass) : This whole thing is about surrendering power.
23:49:12 From phil | eosbros : it is
23:49:16 From Josh Kauffman EOS Canada : Ravi everyone else who meshes into the network will then verify before going live
23:49:18 From Ben SHEOS : reasons will help us for tomorrow
23:49:19 From phil | eosbros : people keep booting and changing the rules
23:49:23 From phil | eosbros : this is counterproductive
23:49:37 From Timothy Lewis : guys this call is going way long.
23:49:53 From david : Good point, if a BP is not ready and is a no-go, then perhaps they aren’t ready to be a BP. They need to have a P0 or P1 bug for a no-go.
23:49:55 From Ravi (BlockPro) : Josh, makes sense.
23:50:02 From winlin-EOSBIXIN : what is the result in the Validation Telegram group?
23:50:07 From Aaron (Greymass) : You need to be able to deal with such a minor bug
23:50:27 From Eric - sw/eden : ABP should be allowed to prepare.
23:50:31 From MAO EOSREAL : telegram Channel is less than 2/3
23:50:43 From phil | eosbros : do you want me to email you from my domain
23:50:49 From Ben SHEOS : agree with Eric
23:50:49 From phil | eosbros : I dont understand why i keep being booted
23:51:00 From Yvonne@eoshenzhen : agree with Eric
23:51:03 From Timothy Lewis : some of us no go’s are ready enough to launch a full chain at any time. doesn’t mean lack of ability.
23:51:21 From Angelia@EosStore : I don't know the Validation Telegram group
，and none tell me
23:51:48 From Douglas Horn | EOSAmericas : We created a process. We should stick it out.
23:52:04 From Marek Eos Emerge Poland : great
23:52:06 From Weifeng@EOS.LAWYER : let ABP to prepare
23:52:16 From Dean Free Space : please add me to telegram voting channel.
23:52:26 From phil | http://www.eosbros.eu/ : this is messed up that a bunch of people arbitrarily are decide which BPs get to participate/vote or not
23:52:32 From Ben SHEOS : 12 hours should be enough time to prep
23:52:35 From Yvonne@eoshenzhen : 1. We donnot think we can go without matching the exact number of Token from ETH to the existing v1.0.0 chain
2. We donnot think we can go without a solid voting platform
23:52:41 From Yvonne@eoshenzhen : We can wait for the subsequent version
23:53:14 From Albert-EosThu : please add me to telegram voting channel.
23:53:25 From ZhaoYu - EosLaoMao : Then you don’t connect to this chain @eosshenzhen
23:53:30 From phil | http://www.eosbros.eu/ : they only allow voting by people who will vote in their favor
23:53:35 From ZhaoYu - EosLaoMao : Printing is settled
23:53:37 From Douglas Horn | EOSAmericas : BEN STOP SPINNING!
23:53:42 From Weifeng@EOS.LAWYER : 1. different opionion, and we can vote, 2, voting will be based on cleos, these are non version related
23:53:47 From Greg | EOSsxsw : It sounds like some block producers are purposely dragging their feet. How long will let this go on? Those ready to GO should break away
23:54:08 From phil | http://www.eosbros.eu/ : can you comment on booting BPs from this chat too?
23:54:09 From Timothy Lewis : thomas said we will have voting properly in zoom
23:54:17 From phil | http://www.eosbros.eu/ : I have verified my identity several times
23:54:41 From Ben SHEOS : anyone can add to that channel
23:54:52 From Ben SHEOS : it’s a super group
23:55:00 From John | discoverEOS.space : people who vote no are voting wrong
23:55:03 From Albert-EosThu : please add me to telegram voting channel.
23:56:06 From Douglas Horn | EOSAmericas : Any BPCs who have been block producers on major testnets should be valid.
23:56:25 From zformular@EOSBepal : someone please invite me? @Bepal_admin
23:56:49 From phil | http://www.eosbros.eu/ : thats the problem
23:56:51 From Weifeng@EOS.LAWYER : invite me @weifeng in telegram, thanks.
23:57:07 From zformular@EOSBepal : i can increase go count!!
23:57:22 From phil | http://www.eosbros.eu/ : many people have been trying to say the software is not ready
23:57:28 From phil | http://www.eosbros.eu/ : but you are booting us before we get to explain
23:57:38 From Weifeng@EOS.LAWYER : third vote
23:57:52 From John | discoverEOS.space : can we vote on whether theres another vote first
23:57:55 From Xavier : Please include me in telegram channel
23:58:07 From Xavier : @xaviercr
23:58:07 From Timothy Lewis : guys this is all going in circles.
23:58:08 From phil | http://www.eosbros.eu/ : that was what dan said
23:58:16 From Weifeng@EOS.LAWYER : version definite is not a blocker
23:58:16 From phil | http://www.eosbros.eu/ : its definitely possible it is a p1
23:58:37 From Weifeng@EOS.LAWYER : we need easy way to "GO"
23:58:46 From Josh Kauffman EOS Canada : EOS Lawyer, please send info that you are a BP. I see you only as a dApp?
23:58:56 From Weifeng@EOS.LAWYER : because "NO GO" is not objective
23:59:11 From Weifeng@EOS.LAWYER : https://eos.lawyer
23:59:30 From Weifeng@EOS.LAWYER : https://steemit.com/@eos.lawyer
23:59:48 From Weifeng@EOS.LAWYER : eos.lawyer is a BPC
23:59:53 From Josh Kauffman EOS Canada : Great. thanks!
23:59:54 From John | discoverEOS.space : mitch is a genius
00:00:26 From Xavier : Who are the admins?
00:00:51 From Lievin - EOSYS : do you know the exact time when the 1.0.2 release?
00:01:02 From Weifeng@EOS.LAWYER : thanks Josh
00:01:18 From Kurt - BPAC : Dan said tomorrow EOD
00:01:23 From Douglas Horn | EOSAmericas : Voting on Keybase is a good suggestion
00:01:43 From John | discoverEOS.space : I have an AOL server we could use
00:01:58 From Yasong “matt” Shi UnlimitedEOS : what kind of credential will be need to be qualify as a voter
00:02:17 From phil | http://www.eosbros.eu/ : ^^
00:02:28 From phil | http://www.eosbros.eu/ : I am worried about this authoritarian approach
00:03:05 From Douglas Horn | EOSAmericas : Short of any unknown issue, EOSAmericas will be voting “Go” in the next vote. We will examine issue #3918 in the interim.
00:03:33 From Edward - EOS Land : 北京时间早上9点在Zoom里再投Go/No Go
00:03:57 From Edward - EOS Land : 周六早上9点
00:04:15 From Marc-Antoine Ross EOS Canada : Phil (Eosbros), name 1 BP that can vouch for you and we will trust your participation
00:05:35 From phil | http://www.eosbros.eu/ : Greg (sxsw) can vouch for me
00:05:37 From Dennis : all BP's have known contact details, survey monkey link sent to all verified BP email addresses
00:06:04 From Johnny5 : Thanks everyone - what an amazing social experiment.
00:06:17 From Johnny5 : :)
00:06:22 From Weifeng@EOS.LAWYER : next time, can we focus "GO" decision?
00:06:28 From david : If a BP votes No-go they need to reveal a P0 or P1 bug, Otherwise this is indication they aren’t ready with their OWN code
00:07:11 From Albert-EosThu : please add me @alberteosthu
00:08:33 From Weifeng@EOS.LAWYER : thanks everyone.