EOS Launch Update - GO / No Go Call details

in #bitcoin6 years ago (edited)

fullsizeoutput_b94.jpeg


This is information is directly from the block producers note taking and not my work. It includes the discussions had Regarding the Go - No Go call held on Wednesday June 6 0100 UTC


GoNoGo Call


Wednesday June 6 0100 UTC
Notes from call. See chat logs below.


General Notes:
140+ participants joined the call
JEM was a proxy for Acro, Sw/eden, EOS PH, EOS Rio, EOS Tribe, EOSKH, HKEOS, EOS Viet
Bo (EOS Silicon Valley) was a proxy for EOS Gravity, EOS Cannon, HelloEOS, EOS Beijing, EOS Asia, EOS Store, HuobiPool, Okex
The call was recorded to facilitate vote counting but will not be made public
Call to order
List your names along with your BP candidate. (Going forward for all other calls, please make sure to do this as it facilitates voting and discussion)


  • Question (21:05:28): David Moss: Is 0100 UTC a good time for go/no-go? Is 1300 UTC a good time for launch?
    Resounding yes for 0100 being a good time
    Resounding yes for 1300 launch time of the chain once we have GO

  • Question (21:14:32): Is everyone OK with running a few streams? One is validating chain contents, one is validating software, one could validate security. “Are we agreeing to perform A) security testing, B) user acceptance testing, C) further snapshot validation. All in parallel.”
    Most are in favour of all testing being done

  • Question (21:18:14): Should we wait for the launch so that we can allow a 48-hour window to allow for the security review by the teams in China.
    First time the question was asked:
    Mainly no (but clarified below)

  • Question was later re-asked: we will wait to see the report that is now expected within the next 24 hours
    Potentially indefinite
    Other comments received:
    David Moss (neutral) says that it stalls the actual review
    Mao (EOSReal) says that 7 days, with a rolling 3 day period is what they think they actually need. 48 hours is a start to get a plan.
    Mao (EOSReal) says that some firms have been working on this for up to 40 hours already at this point - based on what they’ve seen so far, they figure they need the 7 days to have a better idea of how things look
    If we wait, we should have as many BPs who want to join a testnet to be tested
    Bo (EOS Silicon Valley, proxy) gave a rundown of the desire by Chinese teams to conduct security audits, code audits…
    They will deliver a report on security level of overall EOS system: both the network, and eosio/eos software.
    He says that token holders in China prioritize the security over speed. This group is trying to represent the token holders and not only the Block Producers
    Arguments for and against testing now:
    This has been a known launch date for a year
    The codebase has only been solidified for less than a week so it was impossible to test prior to last week
    Will the testing ever stop?
    Block Producers auditing other Block Producers security infrastructure right now is very odd/could be seen as patronizing
    Timothy (LibertyBlock) said that it was a DoD contractor who was doing this testing
    This is an elegant way by the Chinese community to have a third party to do the testing
    If we wait, what else can do in that 48-hour timeframe? What other tests should be run?

  • Question (21:41:18): Do we block launch for another 48 hours to let Asian group perform another security test?
    ~20 yes, notes:
    Let's wait but put a cap on the maximum amount of delay
    ~8 no, notes:
    No for preventing launch, however security testing should still happen with caution to Exchanges
    "let it go"
    (Staking mechanism protects us)

  • Question (21:44:09): Go or No Go? (at 1300 UTC)
    Mixed again.
    This is agreed to in the end, so we didn’t count all votes. See logs for details.
    Point: We need to have a proper voting tool decided on for next call
    So far the idea is to use the current method of voting within Zoom as it’s already integrated and we know that everyone can access it

  • Question (21:50:00): Is everyone confident in the contents of the chain 579a?
    Resounding yes.
    No from Jem (proxy) and Timothy (LibertyBlock). They voiced concerns regarding supply going over 1B and how that could be seen by the community/media.

  • Question: Is everyone confident in the contents of the chain 0d6c?
    Resounding no - reasons given: couldn’t connect when tried, account names failed, too many forks to properly connect when trying.
    Discussion Topic - 1 billion tokens versus added coin supply:
    Jem (proxy) feels the optics of anything above 1B is terrible and hard to get buy-in
    David Moss (neutral) reports that some unnamed person with great influence mentioned his wish to see “printed“ tokens pay for RAM, in agreement with the 579a chain.
    Most on the call seemed to agree with this strategy
    Jem’s (proxy) vision of 1B tokens to take from eosio.unregd was proposed, and voted no (“print”) by most (22:08:36),

  • Questions by David Moss (neutral) to Alexandre Bourget (EOS Canada)
    David Moss asked: To start the entire network, 1 group launches 1 ABP. Is that correct?
    Alexandre: Yes. Correct.
    David Moss: So should we create a new chain with 1 ABP, or should we utilize the 579a chain?
    Seems to be decided that this chain (597a), for now, is the candidate.
    Question (22:14:45): Should we start over a brand new chain for launch?
    Resounding no, notes:
    “Not if it passes validation and security checks.”
    “If the snapshots (frozen chains) have already been validated as complete and ready, then No.”
    Some yes comments;
    “put two side together”
    “yes as validation is quick and so is standing it up.”

  • Question (22:18:13): Should EOS BIOS restart a new chain, hand off to GhostBusters as ABP and allow for them to handle securely holding the chain until 15% voting threshold is reached
    Lots of yes. David Moss (neutral) would have liked to see this agreed upon for the sake of unity, but Jem (proxy) said that they had no specific desire for this to be the case.
    Going Forward:
    The 597a chain should be the chain to which everyone will connect
    Mao (EOSReal) received word during the call that they will receive the audit report sooner than later. Probably within 24 hours.
    Not confirmed if this is full report, or just preliminary.
    The chain that should be tested by the security firms will not contain full snapshot so to be clear it’s a testnet. Then all Block Producers are invited to join so that they would receive the benefit of the testing.
    Reminder to utilize the UAT spreadsheet so that we can continue to compile test cases and results
    Next Meetings:
    June 6, 1300 UTC: to get consensus on remaining points not covered yet
    Test plan & timeline
    ABP selection
    Meshing and ABP protection
    More?
    June 7, 0100 UTC: the next go/no go discussion, hopefully with the initial security report in hand


Notes on next page

CHAT LOGS


21:04:36 From JoseT -eosMeso : 1300UTC is good for us
21:05:12 From Sheldon Huang : Is 1:00 UTC is go-know-go call is good for the world?
21:05:12 From JoseT -eosMeso : 0100UTC go or no go?
21:05:27 From Sheldon Huang : 13:00 UTC for
21:05:28 From Thomas Cox (not a BP) : Is 0100 UTC acceptable for the next Go-NoGo Call?Is 1300 UTC Wednesday an acceptable time for YOU
21:05:30 From Nathan | GenerEOS : 01:00 go/no go follow by 13:00 “go time”
21:05:36 From Alexandre Bourget - EOS Canada : No
21:05:37 From Nate D - Aloha EOS : YES to 0100 go/no
21:05:39 From Denis | EOS Nation : +1 GoNo call (tonight is good)
21:05:41 From Ross (EOSphere) : Yes
21:05:43 From Alexandre Bourget - EOS Canada : 1300 UTC is best time for worldwide sync.
21:05:43 From Craig@BlockSmith : yes
21:05:44 From Sheldon Huang : yes
21:05:44 From JoseT -eosMeso : yes
21:05:44 From Buddy Deck - EOS New York : 0100 UTC work for go/no
21:05:44 From Tim Ogilvie | Staked : Yes
21:05:46 From Sheldon Huang : YEs
21:05:47 From Peter Bue : 1300 UTC go
21:05:48 From Celu : yes
21:05:49 From Nathan | GenerEOS : yes
21:05:49 From Syed Jafri : Yes
21:05:49 From santhosh - EOSNodeOne : 0100 Yes for go/nogo
21:05:50 From winlin-EOSBIXIN : yes
21:05:52 From MAO EOSREAL : yes
21:05:52 From James Sutherland - Cypherglass : 01:00UTC yes
21:05:52 From Cryptosufi - Bitspace : Yes
21:05:55 From Mr Fox : yes
21:05:55 From Alex - EOS SOCAL : yes
21:05:55 From Sheldon Huang : Yes
21:05:56 From Edgar - EOS Costa Rica : Yes
21:05:56 From Rick Schlesinger - EOS New York : yes
21:05:58 From Andrey | BlockEOS.io : yes
21:05:59 From Tim | GenerEOS : Yes
21:06:10 From elliot@ EOS Pacific : Yes
21:06:17 From Nathan | GenerEOS : This is the first go/nogo, but if we are no go the next one tmrw at 01:00
21:06:17 From Sam @ EOS Dublin : Yes
21:06:57 From jorfermo@EOSMetal : yes
21:07:14 From Mr Fox : ok
21:07:18 From yvonne@eoshenzhen : ok
21:07:27 From 彭赟-EosThu : ok
21:07:35 From Ed S. EOSAmericas : yes
21:08:02 From Jacky - JEDA : yes
21:08:04 From [email protected] : 1300 UTC seems to be the best time for a global call. And that's been pretty effective in the past since bios boot stage 1
21:08:19 From Alexandre Bourget - EOS Canada : Launch time = 1300 UTC, yes. Best worldwide sync.
21:08:23 From Buddy Deck - EOS New York : yes 1300 UTC works for us
21:08:23 From Thomas Cox (not a BP) : Shall launch TIME (at any day) be at 1300 UTC on the chosen day?
21:08:25 From Nate D - Aloha EOS : YES to 1300 launch time
21:08:25 From Denis | EOS Nation : yes for 1300UTC launch time
21:08:26 From Marc-Antoine Ross - EOS Canada : Yes
21:08:26 From Nathan | GenerEOS : yes
21:08:26 From JoseT -eosMeso : shall go time be 1300?
21:08:28 From Tim Ogilvie | Staked : Yes
21:08:30 From Tim | GenerEOS : Yes
21:08:30 From Craig@BlockSmith : yes
21:08:31 From JoseT -eosMeso : yes
21:08:31 From Ross (EOSphere) : Yes
21:08:31 From santhosh - EOSNodeOne : Yes 1300 UTC for launch.
21:08:33 From jorfermo@EOSMetal : yes to 13:00 launch time
21:08:35 From James Sutherland - Cypherglass : Launch 13:00UTC - yes
21:08:40 From lukestokes (eosDAC) : Yes on the time (but no day yet specified)
21:08:46 From Sam @ EOS Dublin : Yes to 1300 UTC launch time
21:08:47 From Mr Fox : ok
21:08:48 From Kevin Rose - EOS New York : Yes
21:08:48 From Cryptosufi - Bitspace : yes 13.00 UTC
21:08:52 From Rick Schlesinger - EOS New York : yes
21:08:55 From Peter Bue : yes
21:08:59 From Celu : yes 1300 UTC works
21:09:16 From Syed Jafri : Yes
21:09:22 From elliot@ EOS Pacific : yes
21:09:22 From Peter Bue : Perhaps we should prefix the question number on these responses so it is a little more clear?
21:09:25 From winlin-EOSBIXIN : yes
21:09:50 From 彭赟-EosThu : yes
21:09:52 From Jacky - JEDA : yes
21:10:03 From Alex - EOS SOCAL : yes
21:10:07 From MAO EOSREAL : yes
21:10:18 From Tyee Noprom - EOSpace : yes
21:11:00 From [email protected] : yes
21:11:48 From Alexandre Bourget - EOS Canada : ----------------------------- new question -----------------------
21:11:52 From Alexandre Bourget - EOS Canada : ------------------------------------------------------------------------
21:11:55 From Alexandre Bourget - EOS Canada : -------------------------------------------------------------------------
21:12:57 From Tyee Noprom - EOSpace : 1. 安全测试和功能性测试
21:13:10 From Alberto - EOS Venezuela : yes
21:13:57 From Buddy Deck - EOS New York : The call is at max capacity!
21:14:32 From Thomas Cox (not a BP) : Are we agreed to perform (A) security testing and (B) User Acceptance Testing and (C) further snapshot validation (if any) in parallel, i.e. at the same time?
21:14:33 From Buddy Deck - EOS New York : Can non-BPCs please drop out so BPC can enter
21:15:01 From Syed Jafri : If you are not a BP, please leave
21:15:16 From Syed Jafri : *BPC
21:15:18 From Sam Sapoznick - NOT a BPC : Marc-Antoine is trying to up the capacity to 200
21:15:18 From Tim | GenerEOS : Yes
21:15:22 From Stuardo Rodriguez : yes 2 chains for testing in parallel
21:17:18 From Sam Sapoznick - not a BP : Capacity 98, there are 2 slots open for more particips.
21:18:02 From winlin-EOSBIXIN : yes
21:18:04 From Nathan | GenerEOS : No
21:18:10 From timothylewis : Yes
21:18:14 From Alexandre Bourget - EOS Canada : QUESITON: SHOULD WE BLOCK A LAUNCH BECAUSE OF 48 HOURS OF SECURITY REVIEW.
21:18:16 From Tim | GenerEOS : No
21:18:17 From JoseT -eosMeso : Block launch for 48 hour security review?
21:18:19 From James Sutherland - Cypherglass : No
21:18:20 From Syed Jafri : No
21:18:22 From Alex : No
21:18:22 From Craig@BlockSmith : no
21:18:27 From Joshua Qiu@EOSeco : no
21:18:29 From Denis | EOS Nation : No - not blocking chain, run security tests in parallel
21:18:31 From Ross (EOSphere) : No
21:18:33 From Andrey | BlockEOS.io : no
21:18:36 From Tim Ogilvie | Staked : No
21:18:40 From Buddy Deck - EOS New York : no blocking run all in parallel
21:18:46 From Alex - EOS SOCAL : No
21:18:49 From jorfermo@EOSMetal : No
21:18:50 From Nate D - Aloha EOS : no
21:18:51 From lukestokes (eosDAC) : No, testing will be ongoing always.
21:19:00 From andrew : no
21:19:01 From jem : EOSrio, EOS se/eden HKEOS EOS tribe EOSDAC yes
21:19:23 From Stuardo Rodriguez : no
21:19:37 From Alexandre Bourget - EOS Canada : No
21:20:01 From Josh Kauffman EOS Canada : REMINDER: EVERYONE PLEASE ADD YOUR BLOCK PRODUCER NAME NEXT TO YOUR NAME. WE DON’T KNOW IF SOME ANSWERS ARE FROM COMMUNITY MEMBERS OR FROM BLOCK PRODUCER CANDIDATES
21:20:06 From elliot@ EOS Pacific : no
21:20:47 From Shenghu Yang - EOS SV : Yes
21:21:01 From Jacky - JEDA : no
21:21:06 From Ricardo-EOSBrazil : is it possible to increase the cap on participants of the call?
21:21:08 From Nathan | GenerEOS : There should be an ongoing secure review/testing/standards committee, block producers can implement these actions in parallel on their infrastructure
21:22:16 From mini Argentina : +1 to Bo
21:22:27 From Peter Bue EOSAmericas : +1 Bo
21:22:35 From Lee@EOS Beijing : +1
21:22:40 From MAO EOSREAL : +1 bo
21:25:26 From Nathan | GenerEOS : The EOS freeze date was set a year ago, I agree with David, why is this happening now and not last week?
21:25:51 From Thomas Cox (not a BP) : In fairness, the code base was changing up until the very last minute.
21:27:15 From Nate D - Aloha EOS : Did the 100 max get resolved? It’s been right at 100.
21:27:15 From Syed Jafri EOS Cafe Calgary : 8 confirmed and 4 potential remote vulnerabilities have been found in the last week
21:27:47 From Shenghu Yang - EOS SV : can anyone share the central repo for all the test we done so far, then all can audit.
21:29:52 From Thomas Cox (not a BP) : Nate - we’re stuck at 100 for now
21:31:49 From jem : EOSrio, EOS SW/eden, HKEOS, EOS Tribe, EOSDAC, AcroEOS, EOSPH, EOSKH, EOSviet:
21:32:11 From jem : More tests all good.
21:33:01 From yvonne@eoshenzhen : More tests all good+1
21:34:51 From Ricardo-EOSBrazil to Marc-Antoine Ross - EOS Canada (Privately) : HI Marc, I've got Sam asking if the 100 limit was increased and if he can rejoin
21:34:54 From MAO EOSREAL : 102 now thank the host to resolve that problem.
21:35:13 From Marc-Antoine Ross - EOS Canada : We can now have 200 participants
21:35:24 From Thomas Cox (not a BP) : You rock Marc-Antoine
21:35:29 From Ricardo-EOSBrazil to Marc-Antoine Ross - EOS Canada (Privately) : thanks
21:35:33 From Nate D - Aloha EOS : Thanks Marc
21:35:56 From MAO EOSREAL : Super, Marc!
21:36:23 From jem - proxy for Acro SW/Eden EOSPH EOSRio Tribe EOSKH HKEOS viet : Confidence more important than speed.
21:36:27 From Alex : Please make survey if everyone agrees to postpone for another 48 hours and wait for that report
21:36:36 From Nathan | GenerEOS : Transactions have to be open for that to happen
21:36:46 From Crystal @ shEOS : Yes to testing. How about we meet in the middle and give 24 hours?
21:37:09 From Timothy Lewis - LibertyBlock : I believe the original request was for 7 days.
21:37:32 From Timothy Lewis - LibertyBlock : 48 hours isn’t a lot of time to test a public release.
21:37:58 From Ricardo-EOSBrazil : indeed. we waited 1 year already... 48h+ is nothing
21:38:02 From jem - proxy for Acro SW/Eden EOSPH EOSRio Tribe EOSKH HKEOS viet : Transactions must be open, so must be done on test net.
21:38:19 From Tim | GenerEOS : Lets put it to a vote.
21:38:42 From Timothy Lewis - LibertyBlock : What about launching as a TESTNET Publicly?
21:38:53 From Alexandre Bourget - EOS Canada : There are endless testnets publicly
21:39:02 From Timothy Lewis - LibertyBlock : Not that have been used.
21:39:07 From Timothy Lewis - LibertyBlock : Jungle was a joke.
21:39:10 From Sam Sapoznick (not a BP) : Please MUTE if you are not speaking.
21:39:11 From Alex : tokens will be locked anyway and no problems with parallel testing or doing that on separate testnet
21:39:21 From Nathan | GenerEOS : ^^^ agreed
21:39:28 From Lee@EOS Beijing : it is public
21:39:29 From Nathan | GenerEOS : We have 72 hours of financial lock down
21:39:31 From Josh Kauffman EOS Canada : WE SHOULD ALLOW SOME TIME FOR TRANSLATION ABOUT WHAT HAS BEEN TALKED ABOUT
21:39:45 From Tim | GenerEOS : Only way to solve this is with a vote
21:39:53 From Alexandre Bourget - EOS Canada : Tim: can you formulate a question ?
21:41:01 From Tim | GenerEOS : Do we want to allow 48 hours for security testing? YES or NO?
21:41:07 From James Sutherland - Cypherglass : +1
21:41:10 From Sheldon Huang : +1
21:41:15 From winlin-EOSBIXIN : +1
21:41:18 From Alexandre Bourget - EOS Canada : Or "Do we prevent a launch to allow 48 hours of security review?" would that be correct ?
21:41:19 From Lee@EOS Beijing : +1
21:41:20 From Stuardo Rodriguez : -1
21:41:21 From Denis | EOS Nation : We have to formally announce this question
21:41:27 From Ben@EOShenzhen : +1
21:41:32 From Crystal @ shEOS : Yes
21:41:34 From Ricardo-EOSBrazil : yes
21:41:37 From Tim | GenerEOS : Correct Alex
21:41:42 From Sam Sapoznick (not a BP) : It seems what would be helpful here is a trustworthy voting platform.
21:41:42 From Timothy Lewis - LibertyBlock : YES.
21:41:48 From Alexandre Bourget - EOS Canada : ----------------------------------------------------------------------
21:41:51 From Alexandre Bourget - EOS Canada : ----------------------------------------------------------------------
21:41:53 From Luis Fernando EOSMESOdotio : Yes
21:41:53 From Alexandre Bourget - EOS Canada : ---------------------------------------------------------------------
21:42:10 From Alex : I would formulate that: Do we block launch for another 48 hours to let Asian group perform another security test?
21:42:11 From Peter Bue EOSAmericas : Sam Sapoznikc, I completely agree this form of voting is clumsy.
21:42:21 From Timothy Lewis - LibertyBlock : YES.
21:42:22 From David | EOS42 : Yes - 100%
21:42:24 From nickeosfish : Yes
21:42:24 From Syed Jafri EOS Cafe Calgary : Yes
21:42:24 From winlin-EOSBIXIN : YES
21:42:25 From Sheldon Huang : Yes
21:42:26 From Dr Ye - TChain : Tchian - Ye
21:42:26 From jem - proxy for Acro SW/Eden EOSPH EOSRio Tribe EOSKH HKEOS viet : Yes
21:42:26 From James Sutherland - Cypherglass : No
21:42:27 From Peter Bue EOSAmericas : Yes
21:42:27 From Igor Lins e Silva : YES
21:42:27 From kedar : yes
21:42:28 From Tim | GenerEOS : No
21:42:31 From Nathan | GenerEOS : No (Staking mechanism protects us)
21:42:32 From Alex : no
21:42:33 From Celu - Blockgenic : yes lets wait
21:42:34 From [email protected] : YES
21:42:35 From Craig@BlockSmith : no, do not delay launch
21:42:36 From Hugo - EOS Silicon Valley : Yes
21:42:37 From Jialin@EOS WTZ : yes
21:42:42 From Yves La Rose - EOS Nation : no
21:42:44 From michael : no
21:42:44 From Syed Jafri EOS Cafe Calgary : Jem is the proxy for multiple BPs, please consider that
21:42:49 From Alberto - EOS Venezuela : No
21:42:56 From Denis | EOS Nation : No for preventing launch, however security testing should still happen with caution to Exchanges
21:43:01 From Troi Bryan : eos cafe No. "let it go"
21:43:12 From [email protected] : DOT NOT DELAY ANY MORE
21:43:23 From Nate D - Aloha EOS : No
21:43:45 From Jacky - JEDA : No
21:43:48 From Celu - Blockgenic : yes lets wait but put a cap on the maximum amount of delay
21:43:54 From Ross (EOSphere) : no
21:44:09 From Timothy Lewis - LibertyBlock : ————————NEW VOTE ON NO OR YES GO -----
21:44:16 From elliot@ EOS Pacific : yes
21:44:17 From Timothy Lewis - LibertyBlock : NO
21:44:17 From [email protected] : No
21:44:19 From Craig@BlockSmith : go!
21:44:22 From kedar - LibertyBlock : no
21:44:23 From Peter Bue EOSAmericas : no
21:44:25 From Alex : Go
21:44:27 From Denis | EOS Nation : Go - yes
21:44:29 From Tim | GenerEOS : Go
21:44:29 From Nathan | GenerEOS : Yes - go
21:44:31 From [email protected] : Go
21:44:32 From Yves La Rose - EOS Nation : Go - yes
21:44:38 From Alexandre Bourget - EOS Canada : No. Security auditing should be constant. The % of chances we find something in that 48 hours vs any other day in the next years is minimal. We will need to deal with all issues in the future. It is an endless cliff.
21:44:46 From MAO EOSREAL : NO GO
21:44:47 From michael : Go
21:44:53 From Alberto - EOS Venezuela : Go
21:44:56 From Dr Ye - TChain : No Go -
21:45:00 From Jialin@EOS WTZ : no
21:45:06 From Nathan | GenerEOS : https://goo.gl/forms/r434YPhm9hyqDcKE2
21:45:10 From Buddy Deck - EOS New York : no go in 12 hours.
21:45:15 From nickeosfish : No go
21:45:24 From Cryptosufi - Bitspace : no go
21:45:24 From David | EOS42 : No
21:45:29 From Bo - EOS Silicon Valley : No
21:45:31 From jem - proxy for Acro SW/Eden EOSPH EOSRio Tribe EOSKH HKEOS viet : No go 12 hours later.
21:45:35 From Tim Ogilvie | Staked : No
21:45:46 From Crystal @ shEOS : +1 tools not sufficient for voting
21:45:48 From Syed Jafri EOS Cafe Calgary : No
21:45:56 From Celu - Blockgenic : No go
21:46:00 From jorfermo@EOSMetal : No
21:46:03 From Pascal eosnetwork : No Go
21:46:05 From Sam @ EOS Dublin : No
21:46:07 From bonnie@eostark : no go
21:46:14 From VC@EOS Gravity : Yes, we eosgravity takes security as the first priority.
21:46:28 From Timothy Lewis - LibertyBlock : https://eos.producer.vote
21:46:36 From Timothy Lewis - LibertyBlock : Is a great start.
21:46:45 From Crystal @ shEOS : No go
21:46:47 From Timothy Lewis - LibertyBlock : NO GO
21:46:54 From Dr Ye - TChain : no go - tchain
21:46:54 From Joshua Qiu@EOSeco : Go
21:46:54 From JoseT -eosMeso : no go
21:46:57 From Nate D - Aloha EOS : Go
21:47:16 From [email protected] : Guillaume@eostitan votes NO GO
21:47:17 From kedar - LibertyBlock : vote.libertyblock.io is available for voting
21:47:24 From Jacky - JEDA : GO
21:47:29 From Peter Bue EOSAmericas : Post the results to where?
21:47:30 From santhosh - EOSNodeOne : No go for now - EOSNodeOne
21:47:31 From nickeosfish : No go - eos.fish - eosfishrocks
21:47:42 From Sean X Anderson sw/eden : no go
21:47:43 From Justin - EOS Silicon Valley : i think its a obvious no
21:47:47 From Marc-Antoine Ross - EOS Canada : No go
21:47:47 From Igor Lins e Silva - EOS Rio : no go
21:47:47 From Edgar - EOS Costa Rica : No go
21:47:49 From Ricardo-EOSBrazil : no go
21:47:50 From Tyee Noprom - EOSpace : NO GO
21:47:55 From David | EOS42 : Recall both Bo and Jem are proxy for multiple BP's with their No votes
21:48:19 From Dr Ye - TChain : can we have access to the chinese wechat BPC group?
21:48:47 From winlin-EOSBIXIN : NO GO
21:48:51 From Cryptosufi - Bitspace : No go for now - From BitSpace
21:48:59 From andrew : no go
21:49:09 From MAO EOSREAL : Let me create a wechat one. Please add me 13501835358 我会建立一个微信群,请加进来
21:49:45 From Dr Ye - TChain : doc309
21:49:46 From Alexandre Bourget - EOS Canada : --------------------------------------------------------------------
21:49:49 From cupide@EOS Pacific : 你可以在这里说呀,微信聊不一定更快把
21:49:53 From Alexandre Bourget - EOS Canada : --------------------------------------------------------------------
21:50:00 From Alexandre Bourget - EOS Canada : ---------------------------------------------------------------------
21:50:02 From Ross (EOSphere) : Yes
21:50:03 From Marc-Antoine Ross - EOS Canada : Yes
21:50:03 From winlin-EOSBIXIN : YES
21:50:03 From Syed Jafri EOS Cafe Calgary : Yes
21:50:05 From Nathan | GenerEOS : yes
21:50:05 From Denis | EOS Nation : +1 for 579a
21:50:06 From Craig@BlockSmith : yes
21:50:06 From Tyee Noprom - EOSpace : Yes
21:50:06 From Alex - EOS SOCAL : yes
21:50:06 From jorfermo@EOSMetal : yes
21:50:06 From Ricardo-EOSBrazil : yes
21:50:08 From Tim | GenerEOS : Yes
21:50:09 From Pascal eosnetwork : Yes
21:50:12 From Cryptosufi - Bitspace : yes
21:50:15 From Nate D - Aloha EOS : yes
21:50:16 From [email protected] : Yes
21:50:17 From Yves La Rose - EOS Nation : Yes
21:50:17 From Buddy Deck - EOS New York : yes
21:50:17 From [email protected] : yes
21:50:20 From Alberto - EOS Venezuela : yes
21:50:26 From Peter Bue EOSAmericas : yes
21:50:27 From Alex - EOS SOCAL : yes
21:50:27 From Jacky - JEDA : yes
21:50:28 From Tim Ogilvie | Staked : yes
21:50:32 From [email protected] : 前几个月干嘛去了,现在才来说test test test
21:50:38 From Dr Ye - TChain : yes. clone of jungle?
21:50:45 From winlin-EOSBIXIN : YES
21:50:53 From jem - proxy for Acro SW/Eden EOSPH EOSRio Tribe EOSKH HKEOS viet : No
21:51:05 From Alexandre Bourget - EOS Canada : --------------------------------------------------
21:51:05 From Timothy Lewis - LibertyBlock : NO
21:51:06 From Alexandre Bourget - EOS Canada : ----------------------------------------------------
21:51:07 From Alexandre Bourget - EOS Canada : ------------------------------------------------------
21:51:10 From Alexandre Bourget - EOS Canada : CHAIN: 0d5c
21:51:15 From [email protected] : 知道不知道中国的bps,过去几个星期做了多少事
21:51:17 From [email protected] : NO
21:51:20 From Marc-Antoine Ross - EOS Canada : No
21:51:22 From winlin-EOSBIXIN : NP
21:51:23 From jem - proxy for Acro SW/Eden EOSPH EOSRio Tribe EOSKH HKEOS viet : no
21:51:24 From winlin-EOSBIXIN : NO
21:51:25 From Timothy Lewis - LibertyBlock : no
21:51:26 From Tyee Noprom - EOSpace : NO
21:51:27 From Denis | EOS Nation : -1 not confident, would not want to launch with that chain
21:51:27 From Craig@BlockSmith : no
21:51:29 From Syed Jafri EOS Cafe Calgary : No
21:51:30 From Andrey | BlockEOS.io : no
21:51:35 From andrew : no
21:51:35 From Jacky - JEDA : no
21:51:40 From Peter Bue EOSAmericas : no
21:51:47 From Nathan | GenerEOS : No - was unable to test - account name failures when I tried
21:51:47 From Craig@BlockSmith : no -- many forks of that chain
21:52:00 From Alex - EOS SOCAL : no, forked off to exclusivity
21:52:10 From James Sutherland - Cypherglass : No -- unable to connect to test
21:52:14 From Buddy Deck - EOS New York : no because of fork concerns
21:52:15 From Denis | EOS Nation : no - currently involved in testnet with fake EOS, will cause forks if all nodes don’t properly sync
21:52:16 From Tyee Noprom - EOSpace : NO, NOT VERIFIED THAT CHAIN.
21:52:22 From yvonne@eoshenzhen : no
21:53:03 From MAO EOSREAL : 真的不是很知道哈,所以希望大家能多来国际参与,或者大家组好群找代表来谈
21:53:52 From Joshua Qiu@EOSeco : 579a +1
21:54:16 From Yu Zhao : 579a +1
21:54:26 From song : 579a +1
21:55:32 From winlin-EOSBIXIN : 579a+1 chian B
21:55:36 From Timothy Lewis - LibertyBlock : Extra block rewards that were not agreed to by the community.
21:55:40 From Alexandre Bourget - EOS Canada : 19,000 EOS added to the 1B to pay for RAM, a gift to users.
Each day: 137,000 EOS is added through inflation.

21:55:59 From cupide@EOS Pacific : 579a +1
21:56:02 From Timothy Lewis - LibertyBlock : Awesome, that was expected and agreed to.
21:57:22 From Denis | EOS Nation : $ cleos get currency balance eosio.token eosio
2.0312 EOS
21:57:35 From winlin-EOSBIXIN : yes less 3
21:57:56 From winlin-EOSBIXIN : we can not exact because of the ramfee is float not the same
21:58:16 From Alexandre Bourget - EOS Canada : ---------------------------------------------------------------------
21:58:18 From Alexandre Bourget - EOS Canada : --------------------------------------------------------
21:58:38 From David | EOS42 : We're unelected block producers - not sure we can vote on this
21:58:49 From Nathan | GenerEOS : This is a consequence of block one bancor ram algorithm, I think we need lesser of two evils
21:59:14 From Alexandre Bourget - EOS Canada : ARE WE COMFORTABLE TO ISSUE MORE EOS TO PAY FOR RAM, AS WELL AS SOME WIGGLE ROOM OF 2-3 EOS?
21:59:19 From jem - proxy for Acro SW/Eden EOSPH EOSRio Tribe EOSKH HKEOS viet : No No No No No No No No No
21:59:25 From Marc-Antoine Ross - EOS Canada : Yes
21:59:25 From Sam Sapoznick (not a BP) : Can the RAM be paid back to users AFTER launch, through part of the 4% WP stream?
21:59:27 From Igor Lins e Silva - EOS Rio : NO
21:59:31 From Tim | GenerEOS : Yes
21:59:42 From Ricardo-EOSBrazil : no - although the rest of the chain content is fine
21:59:49 From Syed Jafri EOS Cafe Calgary : Why are we not changing eosio.token to have a supply reduction function?
22:00:03 From winlin-EOSBIXIN : yes
22:00:08 From Syed Jafri EOS Cafe Calgary : Which can be overwritten once all acts are created
22:00:32 From Joshua Qiu@EOSeco : yes to issue
22:00:34 From Tyee Noprom - EOSpace : yes
22:00:41 From Nathan | GenerEOS : yes
22:00:46 From Craig@BlockSmith : yes, comfortable
22:00:50 From Nathan | GenerEOS : The extra inflation I negligble
22:00:53 From Timothy Lewis - LibertyBlock : I do not have authority to issue more tokens.
22:00:53 From Ross (EOSphere) : Yes
22:00:53 From Alexandre Bourget - EOS Canada : Yes
22:00:56 From bonnie@eostark : yes
22:00:59 From Denis | EOS Nation : yes - eosio for paying for RAM
22:01:04 From jorfermo@EOSMetal : yes
22:01:10 From JoseT -eosMeso : yes.
22:01:12 From Justin - EOS Silicon Valley : yes
22:01:29 From Cryptosufi - Bitspace : yes for eosio paying for ram
22:01:30 From Alberto - EOS Venezuela : Yes
22:01:32 From song : yes
22:01:36 From Ed S. EOSAmericas : yes
22:01:45 From Yves La Rose - EOS Nation : Yes for EOS.io paying for RAM
22:01:54 From Buddy Deck - EOS New York : I would like to know all the options.
22:02:06 From Buddy Deck - EOS New York : or what else is possible
22:02:09 From Denis | EOS Nation : agreed, for options being laid out
22:02:10 From elliot@ EOS Pacific : yes
22:02:11 From David | EOS42 : I do not feel unelected block producers alone can make this decision without knowing what other options we have
22:02:15 From Thomas Cox (not a BP) : Who here feels they understand the question and its implications fully?
22:02:17 From winlin-EOSBIXIN : Yes for EOS.io paying for RAM
22:02:23 From James Sutherland - Cypherglass : Option 1: Take From Unregistered Accounts, Return them later on fallback registration
Option 2: Issue more tokens
Option 3: Borrow from 'unregistered' balance, pay back loan from producer pay over first N days
22:02:28 From Andrey | BlockEOS.io : lets hear the options
22:02:31 From Dean Ipad Mini : should the question be, do you want eosio or user accounts to pay for initial ram?
22:02:56 From Angelia@EosStore : I think eosio pay for RAM first may be well.
22:03:06 From Thomas Cox (not a BP) : Option 4: Borrow from the Block.one account and pay it back within 1 day
22:03:35 From Jacky - JEDA : Yes
22:03:46 From Denis | EOS Nation : +1
22:03:54 From Nate D - Aloha EOS : Yes then.
22:03:55 From Tim | GenerEOS : +1
22:03:58 From Timothy Lewis - LibertyBlock : And thus it was written.
22:04:03 From obsrvr : Agreed
22:04:24 From Alexandre Bourget - EOS Canada : -----------------------------------------------------------------
22:04:26 From Alexandre Bourget - EOS Canada : --------------------------------------------------------------
22:04:27 From David | EOS42 : So with that support the decision is effectively made - all good
22:04:28 From Alexandre Bourget - EOS Canada : ---------------------------------------------------------------------
22:04:53 From Michael EOS Pacific : we should use a voting system
22:05:05 From Peter Bue EOSAmericas : ^^^^^^^ Agreed
22:05:09 From Edgar - EOS Costa Rica : yes
22:05:12 From Denis | EOS Nation : +1 print it, move on!
22:05:13 From Timothy Lewis - LibertyBlock : If he says yes, its good to go.
22:05:14 From Tim | GenerEOS : Yes
22:05:21 From lukestokes (eosDAC) : Yes to inflation to launch the chain AND a commitment to pay it back. This happened in May of 2013 when bitcoin forked. The bitcoin foundation paid people back.
22:05:22 From Alex - EOS SOCAL : Create for creation then have the BPs eat a few rounds of rewards. many of those who will be elected are likely in this chat.
22:05:23 From Thomas Cox (not a BP) : What I’m hearing is, it’s more acceptable to our spirit animal to “print additional tokens” and then burn an equal number of tokens from inflation later.
22:05:28 From obsrvr : Agree
22:05:41 From Jacky - JEDA : agree
22:05:42 From Syed Jafri EOS Cafe Calgary : Yes we can burn that EOS from inflation later
22:05:47 From mini Argentina : highest authority dosent sound good
22:05:53 From Denis | EOS Nation : +1 Thomas, burn inflation later on (big yes!)
22:05:54 From Crystal @ shEOS : will “printing more tokens” adjust the 1Bn number forever?
22:05:57 From mini Argentina : p2p :)
22:05:57 From Tim | GenerEOS : What does our god father say about the security window now?
22:05:57 From Justin - EOS Silicon Valley : that is possible?
22:06:00 From Alex - EOS SOCAL : BPs can just forego some rounds.
22:06:05 From jem - proxy Acro SW/Eden Shenzhen PH Rio Tribe EOSKH HKEOS viet : Borrow from unregulated or b1, then replace from WPF.
22:06:06 From JoseT -eosMeso : yes. move on.
22:06:11 From James Sutherland - Cypherglass : Cypherglass agrees that we should print new tokens. Rob Finch offers to make a video explaining this to the token comunity.
22:06:15 From Nathan | GenerEOS : the moment 15% is achieved we will be printing tokens anyway
22:06:18 From lukestokes (eosDAC) : +1 To Thomas’ point
22:06:19 From Syed Jafri EOS Cafe Calgary : Designate a burn account, burn inflation to match later.
22:06:28 From Kevin Rose - EOS New York : Second Luke Stokes highlighting precedent
22:06:28 From Angelia@EosStore : yes
22:06:28 From Marshall : this is interesting.
22:06:37 From Marshall : FYI this is marshall from EOS.fish
22:06:52 From Rick Schlesinger - EOS New York : Please note that STEEM pays for account creation and this is really no different
22:07:09 From obsrvr : Cheers
22:07:09 From Marshall : HAHAHAHA winlin is hilarious
22:07:13 From Timothy Lewis - LibertyBlock : We could “borrow” from unregistered accounts and reward them later for the contribution from initial BP rewards.
22:07:27 From mini Argentina : -1 to the jem proposal
22:07:30 From Marshall : i agree with JEM actually
22:07:44 From Alexandre Bourget - EOS Canada : ------------------------------------------------------------------------
22:07:46 From Alexandre Bourget - EOS Canada : --------------------------------------------------------------------------
22:07:48 From Alexandre Bourget - EOS Canada : ---------------------------------------------------------------------------
22:08:00 From winlin-EOSBIXIN : haha, we should make sure of the token hodlers's benifit
22:08:36 From Alexandre Bourget - EOS Canada : SHOULD WE DRAW FROM THE UNREGISTERED ACCOUNT TO PAY FOR RAM: ~19,000 EOS ?
22:08:52 From Nathan | GenerEOS : No - issue is safer than “borrowing”
22:09:02 From James Sutherland - Cypherglass : Cypherglass - No
22:09:03 From jem - proxy Acro SW/Eden Shenzhen PH Rio Tribe EOSKH HKEOS viet : And restore from day 1 inflation.
22:09:23 From Thomas Cox (not a BP) : If you prefer to BORROW (from either B1 account or Unreg account) type in BORROW, and if you prefer to PRINT extra tokens and then burn them later, type in PRINT
22:09:37 From Marc-Antoine Ross - EOS Canada : No, issue and burn after 1 day, move on
22:09:38 From Nathan | GenerEOS : PRINT
22:09:42 From jorfermo@EOSMetal : No. No taking money from people
22:09:42 From Alberto - EOS Venezuela : Print
22:09:44 From James Sutherland - Cypherglass : Cypherglass - PRINT
22:09:48 From jorfermo@EOSMetal : PRINT
22:09:54 From Jacky - JEDA : PRINT
22:09:55 From Ross (EOSphere) : Print
22:09:57 From Tim Ogilvie | Staked : Print
22:10:01 From Tim | GenerEOS : Print
22:10:03 From Nate D - Aloha EOS : Print
22:10:04 From Alexandre Bourget - EOS Canada : Print
22:10:04 From Craig@BlockSmith : print! +1 for dan's suggestion
22:10:05 From jem - proxy Acro SW/Eden Shenzhen PH Rio Tribe EOSKH HKEOS viet : BORROW
22:10:08 From Hugo - EOS Silicon Valley : Borrow
22:10:09 From Alex - EOS SOCAL : No. Print them instead of taking from someone's account. BPs can then agree to burn, forego, repay.
22:10:12 From Marshall : Borrow
22:10:13 From Syed Jafri EOS Cafe Calgary : Its not borrow if you don’t have B1’s permission
22:10:14 From Timothy Lewis - LibertyBlock : Borrow
22:10:17 From Celu - Blockgenic : Borrow
22:10:19 From Igor Lins e Silva - EOS Rio : Borrow
22:10:20 From JoseT -eosMeso : print and burbñn
22:10:21 From Peter Bue EOSAmericas : borrow
22:10:23 From mini Argentina : Print
22:10:31 From JoseT -eosMeso : print and burn
22:10:32 From lukestokes (eosDAC) : PRINT AND BURN or BORROW AND RETURN (I’m okay with either approach)
22:10:33 From cupide@EOS Pacific : Print
22:10:35 From Timothy Lewis - LibertyBlock : CHARGE B1. It was the mistake of B1.
22:10:37 From Marshall : borrow
22:10:56 From winlin-EOSBIXIN : NO borrow
22:10:58 From elliot@ EOS Pacific : print , after burn
22:11:19 From Michael EOS Pacific : we can’t take erc20 unregistered
22:11:25 From Yves La Rose - EOS Nation : Print
22:11:27 From David | EOS42 : Print it, borrowing sounds messy
22:11:28 From Denis | EOS Nation : PRINT - Clean it up later
22:11:30 From Igor Lins e Silva - EOS Rio : several unregd accounts will never be recovered
22:11:30 From 彭赟-EosThu : print
22:11:35 From winlin-EOSBIXIN : print
22:11:38 From Buddy Deck - EOS New York : print
22:11:43 From Alex - EOS SOCAL : No dont take from anyone's account. Some people from B1 may be ok. Others may be pressured. Dont take from anybody's account.
22:11:46 From Joshua Qiu@EOSeco : print
22:11:51 From Alex - EOS SOCAL : Print and have the BPs burn.
22:11:52 From Nathan | GenerEOS : I think the optics is everyone got free ram
22:12:00 From Michael EOS Pacific : unregistereds are also property should be protected
22:12:03 From Pascal eosnetwork : Print it
22:12:04 From Alex - EOS SOCAL : they'll be burnt
22:12:05 From Sam Sapoznick (not a BP) : The we explain the answer
22:12:09 From kedar - LibertyBlock : print
22:12:12 From Denis | EOS Nation : RAM expense for creating accounts
22:12:13 From Sam Sapoznick (not a BP) : very clear, fair technical answer
22:12:28 From Crystal @ shEOS : Print with burn back to 1Bn as a condition
22:12:38 From Crystal @ shEOS : And never use the word 'print'
22:12:41 From Cryptosufi - Bitspace : Print it
22:13:21 From Sheldon Huang (EOShenzhen) : print
22:13:25 From Alexandre Bourget - EOS Canada : -------------------------------------------------------------
22:13:27 From Alexandre Bourget - EOS Canada : --------------------------------------------------------------------------
22:13:29 From Alexandre Bourget - EOS Canada : -----------------------------------------------------------------
22:13:30 From Alexandre Bourget - EOS Canada : --------------------------------------------------------------------
22:13:31 From David | EOS42 : "RAM Cost New Account Issuance" fund better Crystal?
22:13:53 From David | EOS42 : Agree - we don't use the word print, we're lining up for trouble
22:14:21 From obsrvr : Anyone that's not been through something like this, welcome to history of launches.
22:14:31 From Syed Jafri EOS Cafe Calgary : No to starting over
22:14:45 From Alexandre Bourget - EOS Canada : SHOULD WE START OVER A BRAND NEW CHAIN
22:14:48 From Tyee Noprom - EOSpace : NO
22:14:49 From Ross (EOSphere) : No
22:14:49 From Tim | GenerEOS : NO
22:14:49 From Alex - EOS SOCAL : No
22:14:49 From Craig@BlockSmith : no! do not start over!
22:14:49 From Denis | EOS Nation : Not starting over (not start a new if network content is agreed)
22:14:50 From Marc-Antoine Ross - EOS Canada : No
22:14:50 From jorfermo@EOSMetal : NO
22:14:51 From Syed Jafri EOS Cafe Calgary : NO
22:14:52 From Marshall EOS.fish : NO
22:14:52 From Jacky - JEDA : NO
22:14:53 From Dr Ye - TChain : no
22:14:54 From Tim Ogilvie | Staked : no
22:14:54 From Nathan | GenerEOS : no
22:14:55 From simon@EOS Store : no
22:14:56 From kedar - LibertyBlock : no
22:15:01 From Yves La Rose - EOS Nation : No - do not start a brand new chain
22:15:02 From Pascal eosnetwork : No
22:15:03 From Nate D - Aloha EOS : no
22:15:03 From Cryptosufi - Bitspace : No
22:15:06 From James Sutherland - Cypherglass : No
22:15:06 From jem - proxy Acro SW/Eden PH Tribe EOSKH HKEOS viet : Yes
22:15:07 From Peter Bue EOSAmericas : No
22:15:07 From [email protected] : no
22:15:07 From Igor Lins e Silva - EOS Rio : No
22:15:08 From Timothy Lewis - LibertyBlock : Not if it passes validation and security checks.
22:15:09 From obsrvr : bu
22:15:09 From Celu - Blockgenic : no
22:15:10 From nickeosfish : No - eos.fish
22:15:15 From Andrey | BlockEOS.io : no
22:15:16 From winlin-EOSBIXIN : NO
22:15:17 From Ricardo-EOSBrazil : no
22:15:18 From lukestokes (eosDAC) : If the snapshots (frozen chains) have already been validated as complete and ready, then No.
22:15:18 From David | EOS42 : Can somebody explain what we gain from restarting?
22:15:19 From Joshua Qiu@EOSeco : yes , put two side together
22:15:19 From JoseT -eosMeso : yes
22:15:28 From khosi - eosAfrica : Yes
22:15:36 From Buddy Deck - EOS New York : yes as validation is quick and so is standing it up.
22:15:36 From Alexandre Bourget - EOS Canada : You cannot do "security chekcs on the Contents of a database
22:16:20 From lukestokes (eosDAC) : I don’t care if we have 2 or 10 validated chains or someone starts one up while we’re talking. As long as we have validated chains, we can flip a coin.
22:17:34 From Alexandre Bourget - EOS Canada : ---------------------------------------------------------------------------
22:17:36 From Alexandre Bourget - EOS Canada : --------------------------------------------------------------------------
22:17:38 From Alexandre Bourget - EOS Canada : -------------------------------------------------------------------------------
22:17:44 From obsrvr : Restart the chain, yes
22:18:13 From Alexandre Bourget - EOS Canada : SHOULD WE RESTART A NEW CHAIN, INJECTED WITH THE CURRENT 579a CONTENTS. AND HAVE GHOSTBUSTER RUN ABP TO 15% UNLOCK ?
22:18:16 From Joshua Qiu@EOSeco : yes
22:18:17 From Timothy Lewis - LibertyBlock : yes
22:18:17 From Luis Fernando EOSMESOdotio : Yes
22:18:18 From kedar - LibertyBlock : yes
22:18:19 From [email protected] : yes
22:18:21 From simon@EOS Store : yes
22:18:21 From Buddy Deck - EOS New York : yes yes yes bring this community a fresh start
22:18:21 From jem - proxy Acro SW/Eden PH Tribe EOSKH HKEOS viet : No. Ghostbusters has no need to participate.
22:18:21 From obsrvr : Yes
22:18:21 From Crystal @ shEOS : Yes
22:18:22 From mini Argentina : Yes +1
22:18:23 From Celu - Blockgenic : yes
22:18:23 From nickeosfish : Yes - eos.fish
22:18:24 From Kevin Rose - EOS New York : yes
22:18:25 From David | EOS42 : Yes
22:18:26 From [email protected] : YES
22:18:28 From lukestokes (eosDAC) : Yes
22:18:30 From winlin-EOSBIXIN : No. Ghostbusters has no need to participate
22:18:31 From cupide@EOS Pacific : yes
22:18:32 From Rick Schlesinger - EOS New York : yes
22:18:32 From Alberto - EOS Venezuela : Yes
22:18:32 From Craig@BlockSmith : no, ghostbusters too hard to onboard
22:18:33 From JoseT -eosMeso : y
22:18:33 From Peter Bue EOSAmericas : yes
22:18:35 From bonnie@eostark : yes
22:18:35 From Alex : no
22:18:35 From winlin-EOSBIXIN : No. Ghostbusters has no need to participate
22:18:36 From Ross (EOSphere) : Yes
22:18:38 From cupide@EOS Pacific : yes,perfact
22:18:41 From Hugo - EOS Silicon Valley : Yes
22:18:42 From Denis | EOS Nation : -1 not restarting chain, would delay +2 days
22:18:42 From jorfermo@EOSMetal : no need
22:18:49 From Marshall EOS.fish : Yes if they wish to partcipate -EOS.FISH
22:18:50 From obsrvr : 137 in here now
22:18:51 From elliot@ EOS Pacific : yes
22:18:54 From Nate D - Aloha EOS : If that’s what they want, YES.
22:18:54 From James Sutherland - Cypherglass : No no need
22:19:02 From Denis | EOS Nation : no - why restart if content is the exact same?
22:19:04 From Pascal eosnetwork : Yes
22:19:15 From Nathan | GenerEOS : If we restart set hard time limit for “revalidation”
22:19:19 From Igor Lins e Silva - EOS Rio : restart won't delay much
22:19:22 From Marshall EOS.fish : its technically the same but its more about participation at that point
22:19:22 From Tim Ogilvie | Staked : Yes, as long as peers are not restricted to only those peering via Wireguard.
22:19:24 From Alex - EOS SOCAL : No
22:19:47 From Marc-Antoine Ross - EOS Canada : Yes as long as ABP is voted and enough public nodes allow every BP to mesh
22:19:48 From Igor Lins e Silva - EOS Rio : Yes, we should avoid same genesis
22:19:50 From Dean Ipad Mini : everyone note above, eos core (ghostbusters) voted no to this.
22:21:22 From Sam Sapoznick (not a BP) : Unity
22:21:23 From Denis | EOS Nation : +1 for unity
22:21:27 From Sam Sapoznick (not a BP) : Yes, the community wants unity. A lot.
22:21:29 From [email protected] : +1
22:21:33 From Celu - Blockgenic : yes unity please
22:21:42 From JoseT -eosMeso : we are one
22:21:52 From winlin-EOSBIXIN : +1 unity
22:21:54 From Sam Sapoznick (not a BP) : Everybody wins with unity, esp. token price & therefore BP reward value.
22:21:55 From Ricardo-EOSBrazil : question remains, who would pay for ram on the new chain?
22:22:03 From Nathan | GenerEOS : That question doesn’t remain
22:22:18 From Nathan | GenerEOS : its been voted eosio will gift the ram
22:23:12 From Alex - EOS SOCAL : Unity please. Its not necessary in the slightest. If this will create unity and finally one chain, then let's do it.
22:23:28 From Nathan | GenerEOS : Question:
22:23:40 From Nathan | GenerEOS : Do we need a fresh install to achieve unity?
22:23:48 From Alex - EOS SOCAL : No
22:23:49 From Dr Ye - TChain : how many of you tried both boot and core chains?
22:23:50 From Crystal @ shEOS : +1 to coin flip
22:23:50 From Cryptosufi - Bitspace : +1 for unity. the community will appreciate delay as long as we have unity
22:24:25 From Denis | EOS Nation : +1 EOS-BIOS for ABP
22:24:32 From Dr Ye - TChain : yes
22:24:33 From Alex - EOS SOCAL : +1 Eos bios
22:24:43 From Marshall EOS.fish : @hugo mute your mic
22:26:12 From obsrvr : Translate, please.
22:26:28 From lukestokes (eosDAC) : +1 sooner than later! :)
22:26:38 From cupide@EOS Pacific : Translate, please2
22:26:48 From lukestokes (eosDAC) : Pause for translate?
22:30:46 From Sean X Anderson sw/eden team : Let’s not get together in 12 hours only because it’s easy…
22:30:47 From obsrvr : Google poll, straw poll, whatever, get some numbers counted
22:30:55 From obsrvr : Verify
22:31:28 From Mathieu - EOS Canada : Lets pause to translate please
22:31:37 From obsrvr : Casually glancing at chat yes/no is not enough
22:32:28 From obsrvr : Have used Google polls for published scientific research, but not sure it passes for US.
22:32:32 From Timothy Lewis - LibertyBlock : No
22:32:32 From Thomas Cox (not a BP) : Is the zoom chat sufficient for voting?
22:32:34 From [email protected] : yes
22:32:36 From nickeosfish : They were pretty clear except the ghostbusters apb vote
22:32:36 From Troi Bryan : nope. its better for people to vote in the google doc
22:32:39 From James Sutherland - Cypherglass : Yes
22:32:40 From MacroSam : Yes. I am community non-BP and I thought this went well
22:32:42 From Ricardo-EOSBrazil : yes, for now it seems so
22:32:42 From Kevin Rose - EOS New York : It will be sufficient until we have a close decision.
22:32:42 From Craig@BlockSmith : yes zoom is good for voting
22:32:44 From Rob - Worbli : yes
22:32:51 From Nate D - Aloha EOS : yes
22:32:51 From JoseT -eosMeso : unless its a clos call
22:32:52 From Celu - Blockgenic : yes
22:32:53 From Thomas Cox (not a BP) : Lord no
22:32:55 From Marc-Antoine Ross - EOS Canada : yes
22:32:58 From nickeosfish : Yes zoom is sufficient
22:32:58 From Denis | EOS Nation : +1 Zoom chat for voting, it integrates with the video recording
22:32:59 From Mathieu - EOS Canada : yes
22:33:02 From [email protected] : yes
22:33:02 From Nathan | GenerEOS : Google survey for final go / no go
22:33:05 From Troi Bryan : less social presure. more time to think.
22:33:09 From Swandoyo Hartono : zoom is very suitable for use, thumbs up
22:33:18 From Nathan | GenerEOS : Zoom is good for the soft issues I think
22:33:19 From Sean X Anderson sw/eden team : No - don’t use Zoom for voting … Google forms?
22:33:31 From jorfermo@EOSMetal : good enough
22:33:31 From Troi Bryan : google doc please
22:33:34 From obsrvr : Google Forms
22:33:38 From obsrvr : Or Straw Polls.me
22:33:40 From Thomas Cox (not a BP) : Check this out https://www.swipe.to/2623hc
22:33:43 From Ross (EOSphere) : Zoom is like a preliminary.. would be best to put the vote on a portal
22:33:44 From Cryptosufi - Bitspace : zoom in not most effective voting tool.
22:33:50 From Joshua Qiu@EOSeco : zoom is good,if any tool for voting is better
22:33:57 From lukestokes (eosDAC) : Zoom is not ideal for voting, but the best tool given the limitations. The accounts not on video could be anyone, so it’s not a very good indication of actual BPCs.
22:34:00 From Syed Jafri EOS Cafe Calgary : Need matching of identity
22:34:14 From andrew : For Chineses, it's hard for us to jump the great wall and then connect to the website.
22:34:26 From MAO EOSREAL : 如果有人需要找一个群的话,加我13501835358
22:34:28 From Sam Sapoznick (not a BP) : Yes it is.
22:34:34 From Sam Sapoznick (not a BP) : People will look back and appreciate more.
22:34:34 From Pascal eosnetwork : Tool for voting is better
22:34:39 From Sam Sapoznick (not a BP) : Difficult now, but worthwhile.
22:34:40 From Crystal @ shEOS : Keybase if you want validation
22:34:44 From Crystal @ shEOS : *validation
22:35:00 From andrew : Zoom is good.
22:35:08 From obsrvr : POLL SERVICES: Swipe.to - Google Forms - Strawpoll.me
22:35:12 From winlin-EOSBIXIN : google forms not safe and can NOT make sure the identify of bP
22:35:13 From Michael EOS Pacific : it is a classic Athen democracy
22:35:17 From obsrvr : Recommend Swipe.to or Google Forms
22:35:20 From winlin-EOSBIXIN : google forms not safe and can NOT make sure the identify of bP
22:35:21 From winlin-EOSBIXIN : google forms not safe and can NOT make sure the identify of bP
22:35:21 From obsrvr : Swipe.to is faster
22:35:21 From winlin-EOSBIXIN : google forms not safe and can NOT make sure the identify of bP
22:35:32 From Craig@BlockSmith : we go through 6 votes today... if we do not use zoom we'll get through 0 in a meeting
22:35:35 From Syed Jafri EOS Cafe Calgary : Would not recommend swipe or google forms, less matching of identity than even Zoom
22:35:38 From EOS Argentina : Is one vote per BP, correct?
22:35:39 From winlin-EOSBIXIN : yes
22:35:40 From winlin-EOSBIXIN : google forms not safe and can NOT make sure the identify of bP
22:35:40 From obsrvr : Swipe.to?
22:35:44 From Jialin@EOS WTZ : zoom is good for now
22:35:47 From jockay : Thank you for your effort, the world will remeber, forever.
22:35:54 From winlin-EOSBIXIN : google forms not safe and can NOT make sure the identify of bP
22:35:58 From Denis | EOS Nation : +1 for feedback on security audits
22:36:19 From Dr Ye - TChain : is there a wechat group?
22:36:21 From Nathan | GenerEOS : Bo - can we get a room made asap so we can spin up the testnet clone, get onboarded, tested
22:36:22 From obsrvr : Can't even decide on a poll service, haha
22:36:29 From obsrvr : Swipe.to?
22:36:49 From obsrvr : Strawpoll.me?
22:36:54 From Crystal @ shEOS : Where is the next meeting posted?
22:38:00 From obsrvr : Translate
22:38:34 From obsrvr : 4th female here
22:38:42 From ross_cypherglass : Thanks a ton for coordinating that Mark-Antoine!!!!
22:38:48 From Andrey | BlockEOS.io : thanks!

Sort:  

Great find, obviously upvoted and resteemed! So which chain is which 579a BIOS and 0d6c ghostbusters? Why is there general agreement not to launch ghostbusters?
And what is that issue abotu the 1B+ tokens?

  1. You are correct 579a is EOS Bios and od6c is Core.
  2. I am trying to find out what the concern is regarding Core, but either way, as long​ as one of the chains is good, we get a mainnet.

Hi! This is jlk.news intelligent bot. I just upvoted your post based on my criteria for quality. Keep on writing nice posts on Steemit and follow me @jlkreiss to get premium world news updates round the clock! If you like, just upvote my comment! 🦄🦄🦄

Coin Marketplace

STEEM 0.29
TRX 0.12
JST 0.031
BTC 57038.56
ETH 2908.37
USDT 1.00
SBD 3.65