fC2Fh907

1what do you mean appoint?
2
3Chitty 🅑 - EOS Argentina
4mmm, I guess we will wait for the votes to be counted.. I believe the question was 
5SHOULD WE RESTART A NEW CHAIN, INJECTED WITH THE CURRENT 579a CONTENTS. AND HAVE GHOSTBUSTER RUN ABP TO 15% UNLOCK ?
6
7Nathan Rempel | GenerEOS Sydney
8i thought that question was discarded
9
10Chitty 🅑 - EOS Argentina
11Nathan Rempel | GenerEOS Sydney
12i thought that question was discarded
13why?
14
15Craig Murray - EOS BlockSmith
16because JEM declined on behalf of ghostbusters to do so, he was not particularly interested in that
17
18Chitty 🅑 - EOS Argentina
19Did Jem represent all of Ghostbuster?
20
21Syed Jafri | EOS Cafe / Calgary
22I believe the final was for everyone to join 579a chain once it passes security check phase
23
24Craig Murray - EOS BlockSmith
25Syed Jafri | EOS Cafe / Calgary
26I believe the final was for everyone to join 579a chain once it passes security check phase
27Yes, the offer was made for ghostbusters to pick up that chain and be an ABP for it, which they declined.  But there was overwhelming support of the 579a chain.
28
29Syed Jafri | EOS Cafe / Calgary
30They offerred to join as every other BPC
31
32Craig Murray - EOS BlockSmith
33yes, they offered to join as ordinary BPCs and not be the ABP
34
35Bo - EOS Silicon Valley
36Sure!
37
38Chitty 🅑 - EOS Argentina
39Ok, I must have missed that.. will wait on the report
40
41Luke Stokes
42Chitty 🅑 - EOS Argentina
43Did Jem represent all of Ghostbuster?
44One person representing multiple BPCs seemed counter to DPOS to me, but I'm glad we worked through things and got consensus. Great meeting.
45
46Syed Jafri | EOS Cafe / Calgary
47Luke Stokes
48One person representing multiple BPCs seemed counter to DPOS to me, but I'm glad we worked through things and got consensus. Gre
49You mean proxying votes is counter to DPOS?
50Thats a first
51They delegated their votes
52
53Luke Stokes
54No, proxy is fine if it's on chain and known
55
56Nathan Rempel | GenerEOS Sydney
57Luke Stokes
58One person representing multiple BPCs seemed counter to DPOS to me, but I'm glad we worked through things and got consensus. Gre
59I think the idea is that, randomly assingning a new ABP does not serve much purpose at this point. Everyone regardless of security model is welcome to mesh
60Nathan Rempel | GenerEOS Sydney invited Hugo Yang - EOS Silicon Valley
61
62David P - EOS42
63Luke Stokes
64One person representing multiple BPCs seemed counter to DPOS to me, but I'm glad we worked through things and got consensus. Gre
65Given the timezone of the vote, a proxy representative makes sense in the same way Bo was for multiple BP's
66
67Luke Stokes
68Thanks for clarifying that's an arangement (via proxy) people are comfortable with
69
70Igor Lins e Silva - EOS Rio
71Just for clarification, we see no problem in ghosbusters as the abp if the community decides so, the point jem was stating was simply that we don't have the absolute desire to be the ABP
72
73Nathan Rempel | GenerEOS Sydney
74@bo_eossv @hugo_eossv Is there a testnet already existing or do you need the community to start one?
75
76Syed Jafri | EOS Cafe / Calgary
77could we use jungle?
78
79Igor Lins e Silva - EOS Rio
80Syed Jafri | EOS Cafe / Calgary
81could we use jungle?
82+1
83
84Nathan Rempel | GenerEOS Sydney
85Well, I thought the idea would be to run it against a clone of our candidate
86but as long as the code is the code
87🤷‍♂️
88I just don't want us to fall into the trap that we're all waiting for this security audit - but kept in the dark. Would like to see some action
89
90Nate D - Aloha EOS
91I thought the idea was to start one on production infrastructure
92But yes, needs clarification.
93
94Nathan Rempel | GenerEOS Sydney
95Nate D - Aloha EOS
96I thought the idea was to start one on production infrastructure
97That was my understanding also, so Im eager to swtich our production over to this test
98Nathan Rempel | GenerEOS Sydney invited Dr Ye EOS WashingtonDC - TChain
99
100Bo - EOS Silicon Valley
101Let me do a quick check
102
103Mr Fox
104Bo - EOS Silicon Valley
105Let me do a quick check
106:+1:
107Mr Fox invited Xueyuan She_EOS_WTZ
108
109Stuardo Rodríguez 🇬🇹
110Nathan Rempel | GenerEOS Sydney
111I just don't want us to fall into the trap that we're all waiting for this security audit - but kept in the dark. Would like to
112+1
113
114Nathan Rempel | GenerEOS Sydney
115Is someone already preparing a joint statement to the community regarding the eosio issuance of tokens to gift the genesis accounts with free ram?
116
117Syed Jafri | EOS Cafe / Calgary
118Nathan Rempel | GenerEOS Sydney
119Is someone already preparing a joint statement to the community regarding the eosio issuance of tokens to gift the genesis accou
120Cypherglass offered to do a video
121@finchify
122
123Nathan Rempel | GenerEOS Sydney
124It would be great if we could get a joint steemit/etc to include and share the video
125Dr Ye EOS WashingtonDC - TChain
126Just to clarify, GB/core chain is pretty complicated due to an optional WG (not officially released) - not a serious VPN solution that could be hard to defend in security audits - it is wise to back out
127
128Dafeng Guo - EOS Asia
129Nathan Rempel | GenerEOS Sydney
130I just don't want us to fall into the trap that we're all waiting for this security audit - but kept in the dark. Would like to
131Details will be coming out soon. Things are rolling.
132
133Nathan Rempel | GenerEOS Sydney
134Dafeng Guo - EOS Asia
135Details will be coming out soon. Things are rolling.
136Thanks for that
137
138Syed Jafri | EOS Cafe / Calgary
139Dafeng Guo - EOS Asia
140Details will be coming out soon. Things are rolling.
141Thanks Dafeng, keep us updated!
142
143Bo - EOS Silicon Valley
144Dafeng Guo - EOS Asia
145Details will be coming out soon. Things are rolling.
146:+1::+1:
147Dr Ye EOS WashingtonDC - TChain
148Nathan Rempel | GenerEOS Sydney
149Can we get a group made for the Asian security audit coordination asap
150please get tchain posted
151
152Kevin Rose - EOS New York
153Syed Jafri | EOS Cafe / Calgary
154@eosnewyork, we also need a global statement for this security delay
155We’ve already issued it
156The statement today states the time needed
157https://steemit.com/eos/@eosnewyork/the-eos-mainnet-launch-security-and-software-testing
158
159Steemit
160The EOS Mainnet Launch: Security & Software Testing — Steemit
161Disclaimer: As a token holder, it is important that you do nothing during this period. Never expose your private key… by eosnewyork
162
163Dafeng Guo - EOS Asia
164Igor Lins e Silva - EOS Rio
165+1
166Are we referring to use jungle’s network mesh? I believe most nodes there don’t have prod level infra. We are happy to work with @BohdanCryptoLions if he is interested in helping to set up a new testnet that’s just for security testing.
167
168Timothy Lewis
169Kevin Rose - EOS New York
170https://steemit.com/eos/@eosnewyork/the-eos-mainnet-launch-security-and-software-testing
171Great post.
172
173Syed Jafri | EOS Cafe / Calgary
174I think Bohdan has one of the most experience in the community for launching testnets. He is also a relatively neutral party that can help launch a security testnet
175Would be nice to reach out to him @BohdanCryptoLions
176
177Kevin Rose - EOS New York
178Timothy Lewis
179Great post.
180Group effort. Thanks Tim. If you haven’t posted already please feel free to. This is a statement meant to represent us all.
181
182Nathan Rempel | GenerEOS Sydney
183Syed Jafri | EOS Cafe / Calgary
184I think Bohdan has one of the most experience in the community for launching testnets. He is also a relatively neutral party tha
185+1
186
187Jose Toriello
188+1+1
189Timothy Lewis
190Great post.
191+1
192
193Luke Stokes
194Kevin Rose - EOS New York
195The statement today states the time needed
196I was thinking the same thing. That post covered what we ended up deciding on the call quite nicely. Well done!
197Dr Ye EOS WashingtonDC - TChain
198Syed Jafri | EOS Cafe / Calgary
199I think Bohdan has one of the most experience in the community for launching testnets. He is also a relatively neutral party tha
200+1 happy to help if he Bohdan agrees to take the job
201
202Nathan Rempel | GenerEOS Sydney
203Any other candidates to spin up this testnet if @BohdanCryptoLions isn't available?
204
205mini - EOS Argentina
206I think eos.host was quite good, dont know if those guys are up for it
207the monitor was superv, and they have account creation and a super nice voting system
208
209Dafeng Guo - EOS Asia
210I contacted EOS.host yesterday
211They are happy to help
212
213Craig Murray - EOS BlockSmith
214Kevin Rose - EOS New York
215https://steemit.com/eos/@eosnewyork/the-eos-mainnet-launch-security-and-software-testing
216nice job staying away from calling out these launch cohorts by name.  Well done sir, thanks
217
218mini - EOS Argentina
219Dafeng Guo - EOS Asia
220They are happy to help
221great!
222
223Crystal Rose | :zap:SENSE | :purple_heart:shEOS
224Throwing out some gratitude and kudos to everyone for working hard and giving yourself to this mission. It’s apparent how much time and care has been dedicated. I’m impressed by this group. Thank you! :pray:
225
226Branden Espinoza
227Crystal Rose | :zap:SENSE | :purple_heart:shEOS
228Throwing out some gratitude and kudos to everyone for working hard and giving yourself to this mission. It’s apparent how much t
229I am too.  I made the mistake of sticking my nose into some social media crypto groups today.  They have no idea.  The disconnect between what they are saying and what everyone here is doing is unreal.  This is amazing to be a (small) part of.
230
231Bo - EOS Silicon Valley
232Thanks so much everyone for making EOS possible! Really appreciate it:+1:
233We are running full speed on security testing and will try our best to share as many updates as possible. This won't be a blackbox testing!
234
235Patrick B - Aloha EOS
236Bo - EOS Silicon Valley
237Thanks so much everyone for making EOS possible! Really appreciate it:+1:
238Thanks to you as well Bo!
239Mark-eosantpool invited Mr.Z
240
241Marc-Antoine Ross - EOS Canadaadmin
242All, 
243
244Thanks for the productive call. 
245
246Find below the minutes, if you find anything not accurate, please suggest/comment and we will fix.
247The raw log is included at the bottom of the document.
248
249https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c
250
251Next steps:
252June 6, 1300 UTC: to get consensus on remaining points not covered yet
253    Test plan & timeline
254    ABP selection
255    Meshing and ABP protection
256    More?
257June 7, 0100 UTC: the next go/no go discussion, hopefully with the initial security report in hand
258
259Thanks, good after-mor-night!
260
261Google Docs
262GoNoGo Call
263Wednesday 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, E...
264Marc-Antoine Ross - EOS Canada pinned « All, Thanks for the productive call. Find below the minutes, if you find anything not accurate, please suggest/comment and w»
265
266Daniel Larimer
267David Moss
268All but .1337 of one EOS token has been accounted for...
269That’s 1337.
270
271David Moss
272Ah, interesting. I heard it different.
273Still, a rounding error.
274Printing tokens for RAM startup is a rounding error as well.
275
276Timothy Lewis
277@abourget @marcantoineross did anyone try to implement the RAM cost solution from K Kim of EOSeoul?
278https://gist.github.com/redjade/c22b2d7fcab068af67c0de31724eb710
279diff for adding mitigatebiosramcost on eosio 1.0
280[Photo]
281
282Zhao Yu@ EOSLaoMao.com
283any post about the whole idea?
284
285Timothy Lewis
286From the authoer @resvera: "It compiles well. I didn’t test it. I’m not quite expert on boot sequences. But a developer.
287
288test would be as follows. After Alex method which increases token supply and buys rams for genesis accounts, then input value of migratebiosramcost action will be the amount of token used to buy rams (not value of increased token amount). After migratebiosramcost with correct input, then bancor balance of EOS(CORE) will be clean as initial state of setcode of eosio.system contract. migratebiosramcost can be called only once as I implemented. 
289
290This action is very delicate one. Test should include code reviews and actual push action test."
291
292Jose Toriello
293David Moss
294Printing tokens for RAM startup is a rounding error as well.
295I suggest "issuing" and not "printing" as a better vocabulary, especially given the sensitivity around the subject.
296
297James Sutherland - Cypherglass.com
298Marc-Antoine Ross - EOS Canada
299All, Thanks for the productive call. Find below the minutes, if you find anything not accurate, please suggest/comment and w
300Nice work on this.  Thanks for taking the effort to put this document togeather.
301
302Jose Toriello
303Crystal Rose | :zap:SENSE | :purple_heart:shEOS
304Throwing out some gratitude and kudos to everyone for working hard and giving yourself to this mission. It’s apparent how much t
305+1
306Branden Espinoza
307I am too. I made the mistake of sticking my nose into some social media crypto groups today. They have no idea. The disconnec
308+1
309Marc-Antoine Ross - EOS Canada
310All, Thanks for the productive call. Find below the minutes, if you find anything not accurate, please suggest/comment and w
311+1
312
313Timothy Lewis
314Jose Toriello
315I suggest "issuing" and not "printing" as a better vocabulary, especially given the sensitivity around the subject.
316There has been a potential well written solution to the whole problem that was painstakingly written by @resvera ... Has it been tested? Are we a community that doesn't try to fix issues?
317
318David Moss
319I agree it's a good solution. Would it require restarting the mainnet candidate>?
320
321Timothy Lewis
322It would require a code review first, and then a test.
323
324Nathan Rempel | GenerEOS Sydney
325Question do you want to solve the problem with smart contract edits? You could just load a new eosio.token and go "unissue 11890". then reload the original
326
327Timothy Lewis
328If the test was successful then we would have the opportunity to walk through the boot process as a community.
329
330Nathan Rempel | GenerEOS Sydney
331Timothy Lewis
332If the test was successful then we would have the opportunity to walk through the boot process as a community.
333Have you run his code and tested it?
334
335Timothy Lewis
336We are talking about 2-3 hours to complete a test. I have not run it. It needs to be tested.
337I only learned about it recently, but from the quality of the code, it was well thought out and I was asking who if anyone had tried it.
338
339Marc-Antoine Ross - EOS Canadaadmin
340Timothy Lewis
341I only learned about it recently, but from the quality of the code, it was well thought out and I was asking who if anyone had t
342While the community has voted to move on & the cost/benefice is hard to justify, you are very welcome to propose this solution on the next call. Especially if it's been thoroughly tested by different teams.
343
344Nathan Rempel | GenerEOS Sydney
345Yes, I think if you want to champion new solutions at this point in time the onus should be on you to test, prove, and provide evidence or get like minded individuals to do the same
346Otherwise we're in an endless loop of "hey what about this?"
347
348Timothy Lewis
349Understood. I am now just trying to find out if anyone had tested it, or reasons they anyone may have not wanted to.
350
351Nathan Rempel | GenerEOS Sydney
352Timothy Lewis
353Understood. I am now just trying to find out if anyone had tested it, or reasons they anyone may have not wanted to.
354Looking at the code my concern is that while it may be valid its a lot of change
355Considering validation tools already check every account balance i think something simpler like
356 
357void token::unissue(quantity){
358statstable.modify( st, 0, [&]( auto& s ) {
359       s.supply -= quantity;
360    });
361}
362
363would be preferable in the eosio.token contract, then reconfirm balances = total supply
364Above is obviously invalid code, just making a point
365That said I agree with using tools that don't require contract changes... and burning the inflation through those pre-exisisting tools, personally
366Emily Bush - shEOS invited Autumn Moss Penaloza / shEOS
367
368Yvonne (EOShenzhen)
369Kevin Rose - EOS New York
370We’ve already issued it
371great.thank you
372
373Nathan Rempel | GenerEOS Sydney
374I guess its getting late in North America, but Europe is starting to wake up, looking forward to some updates soon :)
375
376Luke Stokes
377Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer
378You can use this tool to validate yourself.
379Is there a better place to discuss this tool? I had a question about why eosiocpp was removed. I can't compile my token contract to test it. cc @hiwinlin
380
381Sandwich
382Joshua Qiu @EOSeco
383you dont do any thing with snapshot_unregistered.csv?
384https://github.com/EOSIO/eos/pull/2669/files ?
385GitHub
386Draft of eosio.unregd to keep unreg'd Ethereum addr + EOS balances on chain by a...
387The goal would be to all the community to inject the unregistered snapshot, left on chain.. destroy the authority for the eosio.unregd account, and le...
388
389WinLin-EOSBIXIN
390Luke Stokes
391Is there a better place to discuss this tool? I had a question about why eosiocpp was removed. I can't compile my token contract
392you can not find you eosiocpp?
393maybe sudo make install again
394
395Nathan Rempel | GenerEOS Sydney
396Any news guys?
397
398Sharif Bouktila - EOS Dublinadmin
399Next call is 13:00 UTC 6th June 2018
400
401I’ll post Zoom details before here.
402
403Ross (EOSphere)
404Would be great if everyone could complete at least one test.. there don't seem to be many participants in our UAT google doc... https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit?usp=sharing
405
406Google Docs
407EOS UAT - User Acceptance Testing
408Home
409
410
411Create a Case, Record a Test
412Procedure 1: Create a Case
413STEPS
4141, Confirm your case does not yet exist
415a, Click the red Cases tab at the bo...
416
417jem
418Account creation RAM costs solution
419
420We have a total solution for RAM allocation, which rsults in no issuance of new tokens, no borrowing of tokens, and complete accurate final state of all accounts.
421
422During 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.
423
424Just 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.
425
426By 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.
427
428We believe that this simple process is the correct way to create user accounts while maintaining precise suply of total EOS tokens.
429
430Sharif Bouktila - EOS Dublinadmin
431EVERYONE - We have our next Validation Call at 13:00 UTC 
432
433If you are not directly involved in testing / validation, you do not need to attend the call. 
434
435The focus on this call with be establishing what the current status is. 
436
437Agreeing what the focus is for the next 6 hours. 
438
439@samnoble or I will post clear minutes and actions to this group for awareness so nothing is lost in translation.
440
441mao EOSREAL
442jem
443Account creation RAM costs solution We have a total solution for RAM allocation, which rsults in no issuance of new tokens, no
444This is something super.
445
446Jiri Jetmar | EOS Germany | jj@eosgermany.one
447jem
448Account creation RAM costs solution We have a total solution for RAM allocation, which rsults in no issuance of new tokens, no
449I don't want to interfere here, but I think the RAM cost issues is not the real problem. We have lived for centuries in economic systems where at no time is the available money supply known. With EOS we now have a very small and only initial delta - no one really cares. Nobody loses money, nobody gets cheated. But I'm fine with any solution that can be delivered ASAP. Thank you.
450
451jem
452mao EOSREAL
453This is something super.
454Kind of embarassing how easy the solution is. Since we have a snapshot of the chain just prior to resignation, applying it is a 1 minute job.
455Laim Lais joined group via invite link
456Sharif Bouktila - EOS Dublin pinned «EVERYONE - We have our next Validation Call at 13:00 UTC If you are not directly involved in testing / validation, you do not »
457
458Nathan Rempel | GenerEOS Sydney
459jem
460Kind of embarassing how easy the solution is. Since we have a snapshot of the chain just prior to resignation, applying it is a
461I feel like im missing something? Where did the EOS that goes into eosio.ram and eosio.ramfree come from? If you put it "back" in eosio... wasn't the total supply number still increased?
462
463jem
464Nathan Rempel | GenerEOS Sydney
465I feel like im missing something? Where did the EOS that goes into eosio.ram and eosio.ramfree come from? If you put it "back" i
466No
467
468Bohdan CryptoLions 🦁
469Nathan Rempel | GenerEOS Sydney
470Any other candidates to spin up this testnet if @BohdanCryptoLions isn't available?
471I am here, need to sleep sometimes =)
472
473Nathan Rempel | GenerEOS Sydney
474Bohdan CryptoLions 🦁
475I am here, need to sleep sometimes =)
476I feel ya brother
477
478Michael Yeates
479Nathan Rempel | GenerEOS Sydney
480I feel like im missing something? Where did the EOS that goes into eosio.ram and eosio.ramfree come from? If you put it "back" i
481the eos in the ram and ramfee accounts is the exact amount that was spent for  ram by eosio
482
483Sharif Bouktila - EOS Dublinadmin
484Both solutions were fine with me,  please think about how we collectively make a decision and close this one out.
485
486Jiri Jetmar | EOS Germany | jj@eosgermany.one
487Sharif Bouktila - EOS Dublin
488Both solutions were fine with me, please think about how we collectively make a decision and close this one out.
489+1
490
491David P - EOS42
492jem
493Account creation RAM costs solution We have a total solution for RAM allocation, which rsults in no issuance of new tokens, no
494This sounds much more elegant, how difficult is that to implement? As you’ll note from the global voting many BPs seem to just be at a stage of wanting to launch whatever provided there is no security compromise. If this can be done properly on a Core validated chain at the same equivalent stage (or ahead) then we can vote to just move and adopt that with this solution. Coming just with this I think will get a no if it implies any sort of delay. I much prefer this as a launch sequence though for many reasons.
495
496jem
497It was 4 lines of script, total.
498
499Nathan Rempel | GenerEOS Sydney
500I thought this was the process already done, theres still a *supply* surplus, your just moving numbers around. eosio issued  19,832.9750 EOS and 95.5916 EOS did it not? Did these EOS just appear - from where?
501
502David P - EOS42
503Fine so if you can implement and say “we have a chain with this solution and equally well validated” then we can vote directly between the chain to proceed with.
504
505jem
506GB made a snapshot of the chain after injection and immediately before resignation of eosio (done to create base for Acceptance Test Nets), so they do these two transfers, resign, and are back to the same state as the existing paused chain.
507
508Bohdan CryptoLions 🦁
509Nathan Rempel | GenerEOS Sydney
510I feel ya brother
511is testnet still needed? what data use to deploy?
512
513Sharif Bouktila - EOS Dublinadmin
514David P - EOS42
515This sounds much more elegant, how difficult is that to implement? As you’ll note from the global voting many BPs seem to just b
516The question of which chain to launch is bigger.  
517
518It doesn't feel right that we are making it on what I believe is such a small issue. 
519
520How long would it take WP inflation to build to pay for this RAM?   If we calculated that inflation from when each of the chains were established and manually inserted the inflation what would more than cover it and is in keeping with what everyone knew was coming.
521
522Nathan Rempel | GenerEOS Sydney
523Bohdan CryptoLions 🦁
524is testnet still needed? what data use to deploy?
525Would be nice if @bo_eossv and @dftle could provide an update, its been many hours
526
527jem
528No one is arguing which chain to launch. It really doesn't matter.
529
530Michael Yeates
531Sharif Bouktila - EOS Dublin
532The question of which chain to launch is bigger. It doesn't feel right that we are making it on what I believe is such a smal
533we should reach community consensus on these issues
534
535David P - EOS42
536jem
537GB made a snapshot of the chain after injection and immediately before resignation of eosio (done to create base for Acceptance
538So apart from the global politics and niceties of including both bios/core in this process, we actually can just use an equally validated chain as the basis instead with a better solution? That’s what needs to be communicated on the call.
539
540Sharif Bouktila - EOS Dublinadmin
541jem
542No one is arguing which chain to launch. It really doesn't matter.
543Can your approach be applied to B-Chain also.
544
545David P - EOS42
546Michael Yeates
547we should reach community consensus on these issues
548I’d prefer not to have the same BP running the call and setting the questions every time. If Dublin ran a previous then last night was Canada so it’s for another to facilitate it.
549
550jem
551Sharif Bouktila - EOS Dublin
552Can your approach be applied to B-Chain also.
553Yes, if they made the snapshot which had been promised to GB before it was launched.
554
555Sharif Bouktila - EOS Dublinadmin
556David P - EOS42
557I’d prefer not to have the same BP running the call and setting the questions every time. If Dublin ran a previous then last nig
558Would you like to take it?
559I agree
560
561Craig Murray - EOS BlockSmith
562jem
563Account creation RAM costs solution We have a total solution for RAM allocation, which rsults in no issuance of new tokens, no
564Personally I think this issue was closed.  I agree with Dan, we should just print tokens.  We have a 72 hour old chain done this way, we should stick with it
565
566Sharif Bouktila - EOS Dublinadmin
567jem
568Yes, if they made the snapshot which had been promised to GB before it was launched.
569So they would need a new one? Or is it possible on what they have now??   Sorry I need to get this 100% clear.
570
571Michael Yeates
572they should be able to start a snapshot and fix it without rebooting
573
574David P - EOS42
575Sharif Bouktila - EOS Dublin
576Would you like to take it?
577I would normally if people wished, but I’m in a hotel room here in SF with iffy WiFi, don’t trust it based on performance to date
578
579jem
580Sharif Bouktila - EOS Dublin
581So they would need a new one? Or is it possible on what they have now?? Sorry I need to get this 100% clear.
582I don't know. The snapshot had been promised, but was never delivered. I don't know if it was ever made.
583
584Joshua Qiu @EOSeco
585jem
586Yes, if they made the snapshot which had been promised to GB before it was launched.
587can user sell initail ram?
588
589Sharif Bouktila - EOS Dublinadmin
590David P - EOS42
591I would normally if people wished, but I’m in a hotel room here in SF with iffy WiFi, don’t trust it based on performance to dat
592I'll do this one then.   And ask for another Chair for the next one on the call.
593
594David P - EOS42
595Craig Murray - EOS BlockSmith
596Personally I think this issue was closed. I agree with Dan, we should just print tokens. We have a 72 hour old chain done this
597Here’s the point - Dan was asked without any other solution proposed. If we now say it’s slightly messy solution that will require political explanation and justification to community later on this chain, or cleaner solution without any such issues on this chain (and no downside of additional delays), which do you think Dan would choose?
598
599Craig Murray - EOS BlockSmith
600David P - EOS42
601Here’s the point - Dan was asked without any other solution proposed. If we now say it’s slightly messy solution that will requi
602Dan already weighed in on this
603
604David P - EOS42
605I think he’d probably say use the better solution if there’s no delay
606
607Craig Murray - EOS BlockSmith
608there is delay
609
610David P - EOS42
611Craig Murray - EOS BlockSmith
612there is delay
613What’s the delay?
614
615Craig Murray - EOS BlockSmith
616restarting a chain, revalidating it, changing the boot sequence
617
618Joshua Qiu @EOSeco
619i am thinking about sell inital ram, who should pay for this sell
620
621David P - EOS42
622Sharif Bouktila - EOS Dublin
623I'll do this one then. And ask for another Chair for the next one on the call.
624Thanks, I also think you’re trying to be politically neutral here too
625Craig Murray - EOS BlockSmith
626restarting a chain, revalidating it, changing the boot sequence
627Is that correct @jemxpat ?
628
629Zhao Yu@ EOSLaoMao.com
630if user can sell ram, then the only thing fixed by jem’s new solution is the extra 2 or 3 EOS I think.
631
632Michael Yeates
633they cannot sell their initial ram until someone else buys it
634
635Zhao Yu@ EOSLaoMao.com
636so they can, as sell means there are buyers and sellers.
637
638Craig Murray - EOS BlockSmith
639i cannot believe we're still debating this non-issue
640
641Michael Yeates
642if they sell too much of their initial ram then their account will not function well
643
644Craig Murray - EOS BlockSmith
645even Dan knows it's not a real issue
646
647Zhao Yu@ EOSLaoMao.com
648Michael Yeates
649if they sell too much of their initial ram then their account will not function well
650what about I buy some more then sell it?
651
652jem
653Maybe Dan "knows" it. But, it is wrong, and will look very bad to some.
654
655Craig Murray - EOS BlockSmith
656jem
657Maybe Dan "knows" it. But, it is wrong, and will look very bad to some.
658glad you know more than Dan
659you're not even a BP, what is your stake in all this, a non BP who speaks for an entire launch group?
660
661jem
662I'm not a syncophant.
663
664Craig Murray - EOS BlockSmith
665you think you know better than him though, clearly.
666
667jem
668I think he is not omniscient.
669
670Craig Murray - EOS BlockSmith
671no one does
672
673Zhao Yu@ EOSLaoMao.com
674so your solution rounded it up to exactly 1B, and this 70 hours validated by multiple teams serveral times B-chain has a 3 extra EOS
675
676Craig Murray - EOS BlockSmith
677yes, it's just another attempt to delay, not a real issue, that's my take.  Issue is resolved, closed, and yesterday's news.  You'll need a better reason than that to stop progress I hope
678
679Jiri Jetmar | EOS Germany | jj@eosgermany.one
680if we continue to deal with trivialities like this, then we see EOS trading at or below USD 5. That would destroy an enormous value. If EOS were a listed company, the shareholders (EOS Tokenholders) would fire the management that is acting so negligently.
681
682jem
683There is no extra 3 EOS in the chain which ran this. There was precisely 1000000000.0000 EOS.
684
685Zhao Yu@ EOSLaoMao.com
686that I agree
687
688Michael Yeates
689Jiri Jetmar | EOS Germany | jj@eosgermany.one
690if we continue to deal with trivialities like this, then we see EOS trading at or below USD 5. That would destroy an enormous va
691if we dont deal with these issues yet then we will have to face them on a live running chain
692
693Zhao Yu@ EOSLaoMao.com
694Michael Yeates
695if we dont deal with these issues yet then we will have to face them on a live running chain
696so what kind of disasters we are talking about because of these 3 extra EOS?
697
698jem
699It is curently 19k extra.
700
701Zhao Yu@ EOSLaoMao.com
702no
703user can sell ram
704
705Michael Yeates
706Zhao Yu@ EOSLaoMao.com
707so what kind of disasters we are talking about because of these 3 extra EOS?
708public opinion backlash about the 20k tokens added
709
710Zhao Yu@ EOSLaoMao.com
711ram is EOS too
712Dr Ye EOS WashingtonDC - TChain
713what is your most recent total block count that is increasing by the second?
714
715Jiri Jetmar | EOS Germany | jj@eosgermany.one
716Michael Yeates
717if we dont deal with these issues yet then we will have to face them on a live running chain
718But this RAM issue is only an initial topic and the delta is very limited. I do not think that anybody cares..
719
720Zhao Yu@ EOSLaoMao.com
721Michael Yeates
722public opinion backlash about the 20k tokens added
723there’s no 20K, there’s 3 EOS, user can sell ram, ram is EOS
724
725Michael Yeates
726the supply discrepency is 20k
727
728Sandwich
729General Information: Rounding a number after calculations, not before, can reduce accumulative dust.
730
731Zhao Yu@ EOSLaoMao.com
732Michael Yeates
733public opinion backlash about the 20k tokens added
734we will tell public the truth. and the truth is, we give them some free ram. that’s all.
735
736Jiri Jetmar | EOS Germany | jj@eosgermany.one
737Zhao Yu@ EOSLaoMao.com
738we will tell public the truth. and the truth is, we give them some free ram. that’s all.
739+1 .. every bank on the planet has delta in their books. It doesn't bother anyone, because it's negligible.
740
741Stuardo Rodríguez 🇬🇹
742Just to confirm, do we have a call right now? Or in 12 hours?
743
744jem
745One hour later.
746
747Stuardo Rodríguez 🇬🇹
748In 1h thank you
749
750Sharif Bouktila - EOS Dublinadmin
751GUYS - Lets keep it on topic and professional please!
752Dr Ye EOS WashingtonDC - TChain
753may i ask who can turn a node to produce blocks on boot-net?
754
755Stuardo Rodríguez 🇬🇹
756I think jem's solution is valid, and I think it is very easy to re run all automated tests in 30 mins. I think it is easy to launch a "net - d" chain, re run the tests and compare. I think this "net d" adds more value than the already running "net c". We also don't have much to do while the Chinese validation runs. I see it as a good thing to do to kill time during this 24h period anyway
757Dr Ye EOS WashingtonDC - TChain
758tons of things going on if you stay hands on
759
760Stuardo Rodríguez 🇬🇹
761"net d" won't stall more than what we are already waiting
762Dr Ye EOS WashingtonDC - TChain
763anyone who got time think of ways of beefing up the security of the mainnet and the best practices of SDLC/Agile process and best practice on launching the mainnet (production deployment)
764
765Benjamin Wang | EOShenzhen
766EOS is not a stock. The value of EOS is based on trust and consensus.
767
768Syed Jafri | EOS Cafe / Calgary
769David P - EOS42
770Here’s the point - Dan was asked without any other solution proposed. If we now say it’s slightly messy solution that will requi
771I have a feeling Dan just wants the chain up before the hackathon :wink:
772
773Kyunghwan Kim - EOSeoul.io
774I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technically. I hope this article helps to see the whole picture.
775
776https://gist.github.com/redjade/bdbcb10708e165b29d0301c5defa1d83
777on_ramcost.md
778[Photo]
779
780Thomas "Disclaimer" Cox (all opinions mine)
781David P - EOS42
782I’d prefer not to have the same BP running the call and setting the questions every time. If Dublin ran a previous then last nig
783Longer term, a rotating chair is probably wise.
784Dr Ye EOS WashingtonDC - TChain
785Kyunghwan Kim - EOSeoul.io
786I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
787:+1:
788
789Nathan Rempel | GenerEOS Sydney
790David P - EOS42
791I’d prefer not to have the same BP running the call and setting the questions every time. If Dublin ran a previous then last nig
792Can we try to follow a similar format, whoever curates the meeting. It seemed to be highly effective
793
794Thomas "Disclaimer" Cox (all opinions mine)
795An agenda helps
796What is the status of data entry of test cases and test results?
797
798David P - EOS42
799Syed Jafri | EOS Cafe / Calgary
800I have a feeling Dan just wants the chain up before the hackathon :wink:
801:grin: I think you’re right! See you in SF soon? I arrived last night.
802Thomas "Disclaimer" Cox (all opinions mine)
803An agenda helps
804@sharifbouktila want a hand with some thoughts on that? I’ll DM
805Let’s just keep the call positive and productive all, we all want the same thing
806
807Craig Murray - EOS BlockSmith
808I'm very close to canceling my flight and staying home for tulip.  I'm very concerned about the state of the launch and our inability to form consensus about validation, UAT, private networks, security testing, and when to allow a chain to process tx
809
810Jiri Jetmar | EOS Germany | jj@eosgermany.one
811David P - EOS42
812Let’s just keep the call positive and productive all, we all want the same thing
813100% agree!
814
815Syed Jafri | EOS Cafe / Calgary
816David P - EOS42
817:grin: I think you’re right! See you in SF soon? I arrived last night.
818About to hop in a plane in 20 :grin:
819
820David P - EOS42
821Craig Murray - EOS BlockSmith
822I'm very close to canceling my flight and staying home for tulip. I'm very concerned about the state of the launch and our inab
823Understand, no doubt as a senior technologist we need you focused on the launch so if it’s ongoing you can’t really do both.
824Syed Jafri | EOS Cafe / Calgary
825About to hop in a plane in 20 :grin:
826Great, shout me when you’re around. I think Joe of Asia and Steve of Tribe amongst anothers are around later so maybe we can all get out
827
828Craig Murray - EOS BlockSmith
829David P - EOS42
830Understand, no doubt as a senior technologist we need you focused on the launch so if it’s ongoing you can’t really do both.
831Jerry is a far better systems admin than I am.  Likely he can handle anything that comes up.  I'm just concerned right now because we're still running multiple topologies simultaneously and so far the group of BPs are struggling to form consensus on many topics.  It's the uncertainty of the entire launch that has me debating my fight later today
832
833Nathan Rempel | GenerEOS Sydney
834I'm also concerned we haven't heard from our friends in China on a joint testnet to run against and have these audits performed against. I'll be hopeful for an update shortly
835
836Craig Murray - EOS BlockSmith
837a full 3rd party security audit takes a lot of time.  YOu can't do that in a day, it takes weeks to test properly
838
839David P - EOS42
840Craig Murray - EOS BlockSmith
841Jerry is a far better systems admin than I am. Likely he can handle anything that comes up. I'm just concerned right now becau
842Come over, I talk to Gee and all BP's will have access to an all day business work room so we can use it as much as needed once there
843Nathan Rempel | GenerEOS Sydney
844I'm also concerned we haven't heard from our friends in China on a joint testnet to run against and have these audits performed
845@maoyifeng @bo_eossv Are either of you able to help get an update on this?
846
847Nathan Rempel | GenerEOS Sydney
848Craig Murray - EOS BlockSmith
849a full 3rd party security audit takes a lot of time. YOu can't do that in a day, it takes weeks to test properly
850Yes, however being told we'll see results in 24-48 hours and we'll have whitebox testing everyone can participate in... my expectations are a bit high
851
852Sharif Bouktila - EOS Dublinadmin
853https://zoom.us/j/786777697
854
855Zoom Video
856Join our Cloud HD Video Meeting now
857Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
858Call in 7 minutes
859
860mao EOSREAL
861David P - EOS42
862@maoyifeng @bo_eossv Are either of you able to help get an update on this?
863I am still on plane.  Can not join this call. Please update me your progress.
864Hyunwoong JI - EOSeoul.io
865Kyunghwan Kim - EOSeoul.io
866I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
867:+1:
868
869Nathan Rempel | GenerEOS Sydney
870@sharifbouktila on Jungle I *just* tested using my genesis account to successfully create and regproducer successfully
871using 8kb ram, 1EOS/1EOS cpu/net
872
873Brett Jeffery @ EOS the World
874Morning meeting starting
875https://zoom.us/j/786777697
876
877Zoom Video
878Join our Cloud HD Video Meeting now
879Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
880- eoseoul.io DS Lim
881Kyunghwan Kim - EOSeoul.io
882I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
883:+1::+1:
884
885jem
886Kyunghwan Kim - EOSeoul.io
887I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
888Excellent! :+1:
889
890Yongkil Kwon - EOSeoul.io
891Kyunghwan Kim - EOSeoul.io
892I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
893Awesome! :+1:
894Dr Ye EOS WashingtonDC - TChain
895with billions at stake, should we start a small pilot EOS holders group to run the mainnet in production for a while before a massive deployment?
896
897David Moss
898Yes, and there should be more than one.
899
900Nathan Rempel | GenerEOS Sydney
901mainnet in production that's not a mainnet? need to clarify the semantics there
902Dr Ye EOS WashingtonDC - TChain
903the boot-net for now
904
905Nathan Rempel | GenerEOS Sydney
906anyone can already do this... it's just a public test net
907and should be
908
909Craig Murray - EOS BlockSmith
910cryptolions has been doing this for a month or more
911they are currently running latest tag
912Dr Ye EOS WashingtonDC - TChain
913yeah... not with real money though
914
915Craig Murray - EOS BlockSmith
916you cannot run with real money and not be the mainnet
917
918David Moss
919Faucets
920
921Craig Murray - EOS BlockSmith
922once it's real money, it's real money and we've live, you cannot take it down and say "we've found issues we're going to start over"
923
924David Moss
925Or sys
926
927Craig Murray - EOS BlockSmith
928yes cryptolions has faucets
929Dr Ye EOS WashingtonDC - TChain
930we are testing on jungle with faucets
931Dr Ye EOS WashingtonDC - TChain invited Terry Hsiao and 3 more
932
933Nathan Rempel | GenerEOS Sydney
934Very productive call, thanks everyone. I'll look forward to seeing testing results appearing in the spreadsheet, lets not lose sight of that :)
935Perhaps we can add this document to the pin to keep eyes on it: https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit?usp=sharing
936
937Google Docs
938EOS UAT - User Acceptance Testing
939Home
940
941
942Create a Case, Record a Test
943Procedure 1: Create a Case
944STEPS
9451, Confirm your case does not yet exist
946a, Click the red Cases tab at the bo...
947
948Craig Murray - EOS BlockSmith
949that felt like a very productive meeting
950
951David P - EOS42
952So the owner of the channel that was live streaming (and had previous BP meetings) without consent has taken down all of the previous videos.  They appear to be named Malc Silberman
953Could somebody confirm who on this channel represents them or 'EOSBschool', it seems they are not a Block Producer from an intial look
954Craig Murray - EOS BlockSmith
955that felt like a very productive meeting
956Yes, we need to all stay focused on the issues at hand and productive resolution now.
957Benjamin Wang | EOShenzhen invited delin he
958
959Kyunghwan Kim - EOSeoul.io
960Kyunghwan Kim - EOSeoul.io
961I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
962And commented on gist above with accompaning patch for implementing token::unissue as PoC. It compiles but not tested and not quite sure before peer code review and someone's test.
963
964I'm not quite fluent in C++, but it was relatively not too difficult to implement. Curious why this simple and clean solution is not yet done. Anyway, it seems that to implement this solution, cleos subcommands and their unittests is super trivial to developers fluent in C++.
965
966Sharif Bouktila - EOS Dublinadmin
967Does anyone know who in here is from the account who live-streamed that call?
968Else I’ll start removing people who haven’t been active in the past 48 hours in this channel and lock it
969
970Mathieu Boulianne - EOS Canada
971Sharif Bouktila - EOS Dublin
972Does anyone know who in here is from the account who live-streamed that call?
973The Zoom link was shared in other public channels
974
975Hubert Chang-EOSeoul.io
976All I heard was someone saying 'EOSBS'? But maybe  it is best to contact  Mark.
977
978David P - EOS42
979Hubert Chang-EOSeoul.io
980All I heard was someone saying 'EOSBS'? But maybe it is best to contact Mark.
981EOSBSchool - Malcolm Silberman
982
983Sharif Bouktila - EOS Dublinadmin
984Mathieu Boulianne - EOS Canada
985The Zoom link was shared in other public channels
986Crazy it’s why we post the link just before that call , if they aren’t in here already they should let be on the call
987
988David P - EOS42
989I don't know who they are on here
990They probably are on here
991
992Josh Kauffman - EOS Canada
993If we want to keep the calls private, maybe on the next call we take the time to first go thru all participants and remove those who should not be on the call.
994
995Sharif Bouktila - EOS Dublinadmin
996There was 140 today at one point
997
998David P - EOS42
999[Photo]
1000This guy
1001
1002Hubert Chang-EOSeoul.io
1003Maybe our friends in US can help us out.
1004Kevin? :) He seems to know just about everyone
1005
1006Sharif Bouktila - EOS Dublinadmin
1007I don’t think they are private , but hate the idea of someone recording and streaming without consent. 
1008
1009Our position and decisions are market sensitive.
1010
1011Brett Jeffery @ EOS the World
1012Sharif Bouktila - EOS Dublin
1013Else I’ll start removing people who haven’t been active in the past 48 hours in this channel and lock it
1014Understood. But just because we don’t post doesn’t mean we’re not active. @hartparr is very active, but he may not post much. :+1:
1015
1016David P - EOS42
1017Sharif Bouktila - EOS Dublin
1018I don’t think they are private , but hate the idea of someone recording and streaming without consent. Our position and decisi
1019It's a breach of trust above all, I think we are all fine with the contents being released for historical record later but we don't need the distraction of fielding questions from countless others.  Let's hope this doesn't happen again.
1020
1021Sukesh Tedla (EOSGreen)
1022Brett Jeffery @ EOS the World
1023Understood. But just because we don’t post doesn’t mean we’re not active. @hartparr is very active, but he may not post much. :+1:
1024+1
1025
1026David P - EOS42
1027Anyway let's get back to onto more important matters
1028
1029Sukesh Tedla (EOSGreen)
1030David P - EOS42
1031Anyway let's get back to onto more important matters
1032:+1:
1033
1034Sharif Bouktila - EOS Dublinadmin
1035Brett Jeffery @ EOS the World
1036Understood. But just because we don’t post doesn’t mean we’re not active. @hartparr is very active, but he may not post much. :+1:
1037That’s fine , I don’t have the answer just yet.  
1038
1039Reminds me of my post months ago about our mantra of DBAA - “Don’t be an a**hole”
1040
1041Ville Sundell
1042So, is the consensus now, that the new selected ABP will launch their own chain?
1043
1044David P - EOS42
1045Sharif Bouktila - EOS Dublin
1046That’s fine , I don’t have the answer just yet. Reminds me of my post months ago about our mantra of DBAA - “Don’t be an a**h
1047Somebody pin this from Sharif.. sometimes the world needs to hear the sweet tones of an Irishman telling you that
1048
1049Brett Jeffery @ EOS the World
1050not criticizing you, just don’t want to get our team locked out just because we’re not posting much.
1051
1052Sharif Bouktila - EOS Dublinadmin
1053Very good call other than that , well done all!!
1054
1055Craig Murray - EOS BlockSmith
1056Ville Sundell
1057So, is the consensus now, that the new selected ABP will launch their own chain?
1058no
1059
1060Ville Sundell
1061Craig Murray - EOS BlockSmith
1062no
1063Good :laughing: (Personal opinion only, I think the existing chain is good to take over by the appointed ABP)
1064
1065Marc-Antoine Ross - EOS Canadaadmin
1066All, 
1067
1068Thanks for another productive call!
1069
1070PRIORITY: get that testing done! https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ
1071
1072Find bellow the minutes, if you find anything not accurate, please suggest/comment and we will fix.
1073The raw log is included at the bottom of the document.
1074
1075https://docs.google.com/document/d/17cwUuPoaH1NAYfSGgvomSvjTkDrMHdVhLaxCS5t-orQ
1076
1077Next steps:
1078June 7, 0100 UTC: the next go/no go discussion, hopefully with the initial security report in hand
1079    Meshing and ABP protection
1080    Ben from shEOS asks: How can we insure that voting portals are handling private keys well?
1081    More?
1082
1083
1084Thanks, good after-mor-night!
1085
1086Google Docs
1087EOS UAT - User Acceptance Testing
1088Home
1089
1090
1091Create a Case, Record a Test
1092Procedure 1: Create a Case
1093STEPS
10941, Confirm your case does not yet exist
1095a, Click the red Cases tab at the bo...
1096Marc-Antoine Ross - EOS Canada pinned « All, Thanks for another productive call! PRIORITY: get that testing done! https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2»
1097
1098Denis | EOS Nation
1099Syed Jafri | EOS Cafe / Calgary
1100Cypherglass offered to do a video
1101:+1: thanks Cypherglass, your last video was very professional and your messaging was accurate to the current events.
1102Kevin Rose - EOS New York
1103https://steemit.com/eos/@eosnewyork/the-eos-mainnet-launch-security-and-software-testing
1104Amazing :muscle::muscle: we should continue to use the same lingo P0 & P1 when presenting the security audits findings
1105Syed Jafri | EOS Cafe / Calgary
1106I think Bohdan has one of the most experience in the community for launching testnets. He is also a relatively neutral party tha
1107:+1: agreed, Jungle has the most experience in launching new Testnets
1108Craig Murray - EOS BlockSmith
1109nice job staying away from calling out these launch cohorts by name. Well done sir, thanks
1110+1 we should not be putting any labels anymore, we're all in this together
1111Bo - EOS Silicon Valley
1112We are running full speed on security testing and will try our best to share as many updates as possible. This won't be a blackb
1113:muscle: we fully support your efforts! Everyone is very happy you and the other Chinese BPC'S/Community/Exchanges are pushing for this.
1114
1115Looking forward to see these findings (good or bad) We will be more informed on our next steps moving forward after these results surface.
1116
1117David P - EOS42
1118I think from now on we need to all stop referring at all to "Bios", "Core" and any other labels and just focus on the collective solution we implement.
1119
1120Sharif Bouktila - EOS Dublinadmin
1121David P - EOS42
1122I think from now on we need to all stop referring at all to "Bios", "Core" and any other labels and just focus on the collective
1123+1
1124
1125Mr.Z
1126David P - EOS42
1127I think from now on we need to all stop referring at all to "Bios", "Core" and any other labels and just focus on the collective
1128Can't agree more!
1129
1130Ben Sigman
1131David P - EOS42
1132I think from now on we need to all stop referring at all to "Bios", "Core" and any other labels and just focus on the collective
1133What will we call it?
1134
1135Kevin Rose - EOS New York
1136First few digits of the chain ID seems to make sense.
1137
1138Craig Murray - EOS BlockSmith
1139unfortuantely the chain starting in 0d6c has been forked a few times, so it's hard to refer to it just by chain id
1140there is the candidate fork, for which the public endpoints appear to be down.  There is the voting fork of it, which has spoofed the contracts so you can vote and test producer schedule, and then there is the fork of it that was accidental that many of the peers are synced to.  There may be more, i don't know.
1141
1142Sharif Bouktila - EOS Dublinadmin
1143A-Z , hopefully we don’t need > 26
1144
1145David P - EOS42
1146Ben Sigman
1147What will we call it?
1148Anything but labels that are divisive to us reaching consensus for a productive launch - that's just my view.  I think we can implement solutions and select a chain without that.
1149
1150Sharif Bouktila - EOS Dublinadmin
1151Or how about jungle animals - a nod to the super work done there
1152
1153Craig Murray - EOS BlockSmith
1154so there are two chains: 579a which has a single line.  And there is 0d6c which has multiple forks.  For a total of 4 chains I know of...   So chains B, C, D, and E?
1155where C D and E have the same chain ID
1156
1157Sharif Bouktila - EOS Dublinadmin
1158Whatever works
1159
1160Michael Yeates
1161there are no multiple forks
1162we have the one chain and separate private chains for testing
1163out blocks db is available for download and testing
1164
1165Craig Murray - EOS BlockSmith
1166those are forks because they have the same ID
1167that's the definition of a fork
1168it's not derogatory, it's jsut fact
1169i spent sevearl hours yesterday trying to get off the 10k fork and onto the 11k fork.  I was finally successful, but those two chains have the same ID, that's a fork
1170we're talking about a way to describe them that doesn't use these silly team names
1171trying to say they are not forks is just confusing to people... they see the chain ID and think they are on the right one
1172
1173Denis | EOS Nation
1174Marc-Antoine Ross - EOS Canada
1175All, Thanks for the productive call. Find below the minutes, if you find anything not accurate, please suggest/comment and w
1176:+1::+1: Marc is the best scribe ever!
1177
1178Patrick B - Aloha EOS
1179Denis | EOS Nation
1180:+1::+1: Marc is the best scribe ever!
1181career change? :D
1182
1183Denis | EOS Nation
1184Jose Toriello
1185I suggest "issuing" and not "printing" as a better vocabulary, especially given the sensitivity around the subject.
1186Agreed, I think the wording "print vs. issue" for optics the word "issuing" should be used for the global message.
1187
1188CC: Cypherglass & EOS New York
1189Patrick B - Aloha EOS
1190career change? :D
1191:joy: full-time scribe :scroll:
1192
1193Patrick B - Aloha EOS
1194haha
1195
1196Jose Toriello
1197Craig Murray - EOS BlockSmith
1198we're talking about a way to describe them that doesn't use these silly team names
1199+1
1200
1201Denis | EOS Nation
1202Timothy Lewis
1203There has been a potential well written solution to the whole problem that was painstakingly written by @resvera ... Has it been
1204:-1: disagree, attempting to reimplement anything that touches token balances would jeopardize the entire validation process (this is why I mentioned +2 days)
1205
1206If we change anything that's related to the token balance, then we're back at step 0 with zero confidence on that new chain.
1207
1208This type of change would cause a drastic delay (for what reason?)
1209
1210Craig Murray - EOS BlockSmith
1211and woudl also degrate public trust that we are making progress
1212
1213Denis | EOS Nation
1214David Moss
1215I agree it's a good solution. Would it require restarting the mainnet candidate>?
1216🤔 restarting a chain for the sake of testing new code that's untested would be a disaster. I personally would not have confidence in any change to core chain injections.
1217
1218David P - EOS42
1219Timothy Lewis
1220There has been a potential well written solution to the whole problem that was painstakingly written by @resvera ... Has it been
1221If a chain is spun up with this solution, fully validated/tested to the same level as others, then we can vote on whether to use this on the next call.  That I'm fine with, but really the tests and security need to remain the bigger priorities.
1222Alex - EOS SOCAL invited Cesar Diaz EOSoCal
1223
1224David P - EOS42
1225And if nobody does it for the next call then this should be parked given we had reached consensus on the balance if not.  It's not a pretty solution but explainable.
1226
1227Craig Murray - EOS BlockSmith
1228Denis | EOS Nation
1229🤔 restarting a chain for the sake of testing new code that's untested would be a disaster. I personally would not have confiden
1230we've got a network with 80+ hours since injection, tested repeatedly, why on earth would we throw that away if no one can prove it invalid?  That's bad optics, wastes time, and would have a very hard time reaching consensus.  On the call yesterday there was overwhelming consensus that the 579a chain is valid and should be used
1231
1232Denis | EOS Nation
1233David P - EOS42
1234If a chain is spun up with this solution, fully validated/tested to the same level as others, then we can vote on whether to use
1235If we spin up a new chain we're at day 0 again.
1236
1237The advantage of chain 579a is the timestamp, if our timestamp changes for today that means we've only tested this chain for <24 hours
1238
1239deck - EOS New York
1240Denis | EOS Nation
1241If we spin up a new chain we're at day 0 again. The advantage of chain 579a is the timestamp, if our timestamp changes for toda
1242What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
1243
1244Timothy Lewis
1245deck - EOS New York
1246What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
1247+1
1248
1249Denis | EOS Nation
1250{"initial_timestamp":"2018-06-03T13:04:31","initial_key":"EOS7m4uBgRXBM5DbXFX7FTrNiZyRzxfktmto6qQTzc2z3BhgAGHKM"}
1251
1252June 3rd is the timestamp of 579a
1253
1254Timothy Lewis
1255Why does that matter
1256
1257Craig Murray - EOS BlockSmith
1258deck - EOS New York
1259What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
1260it takes more than that.  We want it tested by multiple teams, with multiple tools, and given plenty of time for validation.  You don't rush validation that's why we're still waiting on a chain that's up 80 hours and not processing transactions
1261
1262Denis | EOS Nation
1263The software isn't changing unless we find P0 or P1
1264
1265Timothy Lewis
1266Why? I’d rather a chain that is correct.
1267“These guys can’t even get token issuance right, lol”
1268
1269Craig Murray - EOS BlockSmith
1270we're back to ram again?  ugh
1271
1272Denis | EOS Nation
1273deck - EOS New York
1274What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
1275:-1: more then running a few scripts.
1276
1277Starting a new chain for the sake of it says "we have no confidence in the chain we've booted and validated"
1278
1279David P - EOS42
1280deck - EOS New York
1281What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
1282Exactly.  Buddy is right I don't know why you think this takes long Denis, it doesn't.
1283
1284Denis | EOS Nation
1285Timothy Lewis
1286“These guys can’t even get token issuance right, lol”
1287:-1: so you're against BM's decision and the majority of the BPs?
1288
1289Timothy Lewis
1290Craig Murray - EOS BlockSmith
1291we're back to ram again? ugh
1292I’m just super frustrated that someone may have spent the time to create a real solution and in everyone’s rush to get things done, the solution was completely disregarded.
1293
1294Denis | EOS Nation
1295Timothy Lewis
1296I’m just super frustrated that someone may have spent the time to create a real solution and in everyone’s rush to get things do
1297It's not a solution
1298
1299Craig Murray - EOS BlockSmith
1300what chain uses this solution?  Is this solution coded in github?  Tested?
1301
1302Timothy Lewis
1303Look above at the original post.
1304
1305Craig Murray - EOS BlockSmith
1306what are the p2p addresses so i can sync to this new "proper" chain?
1307
1308Timothy Lewis
1309Have a good day guys, I’m back to work.
1310
1311Jae Chung - HKEOS
1312Craig Murray - EOS BlockSmith
1313those are forks because they have the same ID
1314How else would you run an acceptance testing chain without forking?
1315just wondering
1316
1317David P - EOS42
1318Denis | EOS Nation
1319:-1: so you're against BM's decision and the majority of the BPs?
1320To be fair, nobody had another solution it was a very quick "ah, would this even be acceptable" type check by David Moss.  Nobody has since asked for his view - and it's about our consensus.  As I said, if somebody wants to have that chain and solution ready by the next call, we can talk in through in 5mins, then vote to use that or not instead.  If it's a better solution and there's no time cost to us then it's a win.  If there were some delay impacting our overall timeline fair enough.
1321
1322Craig Murray - EOS BlockSmith
1323David P - EOS42
1324Exactly. Buddy is right I don't know why you think this takes long Denis, it doesn't.
1325it does actually.  One person can run validation in 20 minutes but we have to provide time for BPs all over the world to validate and then get consensus that we are valid.  That's 24-48 hours at least
1326
1327Denis | EOS Nation
1328David P - EOS42
1329Exactly. Buddy is right I don't know why you think this takes long Denis, it doesn't.
1330Starting a new chain for the sake of it is not a good decision.
1331
1332If you don't agree with the RAM purchase, then join another chain that has a different chain injection process.
1333
1334Right now 579a has been validated and nothing is wrong with it
1335
1336David P - EOS42
1337Fair enough guys, I'm just trying to give everybody a chance here and keep us moving forwards.
1338
1339Craig Murray - EOS BlockSmith
1340a new chain is moving backwards unless we find a p0 or p1, we should not start a new chain
1341
1342Denis | EOS Nation
1343Craig Murray - EOS BlockSmith
1344it does actually. One person can run validation in 20 minutes but we have to provide time for BPs all over the world to validat
1345:+1: exactly, global planet wide validation will take forever, just because 3-5 BP's say it's good to go doesn't mean it's validated by the community
1346David P - EOS42
1347Fair enough guys, I'm just trying to give everybody a chance here and keep us moving forwards.
1348We are moving forward, wait for security audits from the Chinese community.
1349
1350If no P0 / P1 problems arise, we decide after all reading the findings and call a Go/NoGo meeting (whenever that day comes)
1351Craig Murray - EOS BlockSmith
1352a new chain is moving backwards unless we find a p0 or p1, we should not start a new chain
1353:ok_hand:
1354Jae Chung - HKEOS
1355How else would you run an acceptance testing chain without forking?
1356This just indicates that that Chain C is a "testnet" and not a "candidate chain"
1357
1358We've only got 1 real candidate chain by your comment
1359
1360Craig Murray - EOS BlockSmith
1361Jae Chung - HKEOS
1362How else would you run an acceptance testing chain without forking?
1363I did not suggest you would
1364
1365Jae Chung - HKEOS
1366Denis | EOS Nation
1367This just indicates that that Chain C is a "testnet" and not a "candidate chain" We've only got 1 real candidate chain by your
1368I wasn't referring to that at all. I was wondering if there's another way to acceptance test an existing chain without forking. My question has been answered.
1369
1370Craig Murray - EOS BlockSmith
1371i think there is a chain paused at 11778 on chain id 0d6c, but it's hard to tell because the public endpoints appear to be down for me.  If that still exists I think it's a candidate chain but not sure
1372
1373Michael Yeates
1374the 1178 chain is in the hands of the community
1375
1376Jae Chung - HKEOS
1377Michael Yeates
1378out blocks db is available for download and testing
1379^
1380
1381Michael Yeates
1382paused and distributed
1383
1384Jae Chung - HKEOS
1385we have a public endpoint that we stopped with the fully synced copy at 11778
1386
1387Craig Murray - EOS BlockSmith
1388who is running the boot node for it?
1389
1390Thomas "Disclaimer" Cox (all opinions mine)
1391David Moss
1392Faucets
1393Real public keys from the snapshot? Or a blank testnet?
1394
1395Michael Yeates
1396Craig Murray - EOS BlockSmith
1397who is running the boot node for it?
1398its anonymous
1399we may have just found something
1400
1401Craig Murray - EOS BlockSmith
1402what are the public endpoints for this paused chain?
1403Peter Bue | EOSAmericas invited James Davis
1404
1405Jae Chung - HKEOS
1406Craig Murray - EOS BlockSmith
1407what are the public endpoints for this paused chain?
1408Craig, we provided you with 6 public endpoints to peer from and how to fully sync through them yesterday. This conversation happened both in the EOS Core channel and Keybase team channel. Must we keep repeating this?
1409Here's a block database you can sync from, for your convenience: https://transfer.sh/OIyZl/boot-mainnet-post-resign-ramfix.tar.gz
1410
1411Craig Murray - EOS BlockSmith
1412as I said I'm having trouble with your endpoints today but if you dont want to hel that's fine
1413dont help
1414
1415Jae Chung - HKEOS
1416"Here's a block database you can sync from, for your convenience" <— is this not "help"? I just provided you with the quickest way to sync up to the chain. Not sure why this may be perceived as not wanting to help you.
1417
1418Sharif Bouktila - EOS Dublinadmin
1419Guys looks like @jaechung was helping,  there is plenty of other channels to discuss endpoints etc..
1420Lets try and keep in here on point.   We can spin up another channel for Which Chain type discussions. 
1421
1422If I'm off topic,  I'd expect someone to nudge me back into line, so please don't take offence.
1423
1424Craig Murray - EOS BlockSmith
1425Sharif Bouktila - EOS Dublin
1426Lets try and keep in here on point. We can spin up another channel for Which Chain type discussions. If I'm off topic, I'd
1427:+1:
1428
1429Denis | EOS Nation
1430Sharif Bouktila - EOS Dublin
1431Lets try and keep in here on point. We can spin up another channel for Which Chain type discussions. If I'm off topic, I'd
1432:+1:agreed, we should keep the discussions on topic.
1433
1434Peter Bue | EOSAmericas
1435Sharif Bouktila - EOS Dublin
1436Lets try and keep in here on point. We can spin up another channel for Which Chain type discussions. If I'm off topic, I'd
1437:+1::+1:
1438
1439Hugo Yang - EOS Silicon Valley
1440Tactical Question for 579a chain: if we decide to promote it as the chain voters / BPCs go, how do we deal with all those “dummy” block after injection? A clean up or leave it there?
1441
1442Denis | EOS Nation
1443Hugo Yang - EOS Silicon Valley
1444Tactical Question for 579a chain: if we decide to promote it as the chain voters / BPCs go, how do we deal with all those “dummy
1445That could be a discussion topic for tonight (I won't be able to attend, in a plane during call)
1446
1447IMO: Having a large amount of empty blocks proves to the community that ZERO transactions have occurred during this validation process, I believe it's a positive for having 60+ hours of empty blocks.
1448
1449The filesize of these blocks is minimal, including them isn't a big deal for "launching"
1450
1451My vote: Keep empty blocks until we launch
1452
1453Ben Sigman
1454Denis | EOS Nation
1455That could be a discussion topic for tonight (I won't be able to attend, in a plane during call) IMO: Having a large amount of
1456So Denis - is it that what you are suggesting is for us to agree to launch with the chain that we already have running as it stands right now with no changes?
1457
1458Timothy Lewis
1459Updated: https://gist.github.com/redjade/bdbcb10708e165b29d0301c5defa1d83
1460on_ramcost.md
1461[Photo]
1462
1463Sharif Bouktila - EOS Dublinadmin
1464Folks I've changed the invite link and removed some people from this group.  ( who I didn't recognise or didn't have a BP name in their name ) 
1465
1466If I removed someone from your team,  feel free to contact me directly.   
1467
1468@marcantoineross and @xebb82 are also admins , and people in here should be able to invite others.
1469
1470deck - EOS New York
1471Sharif Bouktila - EOS Dublin
1472Folks I've changed the invite link and removed some people from this group. ( who I didn't recognise or didn't have a BP name i
1473Thanks. Do we also want to be careful with who we share the zoom links?
1474
1475Sharif Bouktila - EOS Dublinadmin
1476If anyone has any suggestions on that, please let us know.  It needs to be public enough so everyone can get it, but private enough not to spread unnecessarily for now.  
1477
1478Can obv put passwords but posting here is kind of the same thing. 
1479
1480I think the message sent out was probably clear enough that until we have a consensus we don't want calls streamed.
1481
1482Rob Finch - Cypherglass.com (Block Producer)
1483Syed Jafri | EOS Cafe / Calgary
1484Cypherglass offered to do a video
1485Happy to do a video. Please send me any details you’d like conveyed.
1486
1487Thomas "Disclaimer" Cox (all opinions mine)
1488I had random tourists watching several of my breakout calls the last few days. I gave them three chances to rename themselves with real names plus their BP, then booted them
1489
1490Sharif Bouktila - EOS Dublinadmin
1491Thomas "Disclaimer" Cox (all opinions mine)
1492I had random tourists watching several of my breakout calls the last few days. I gave them three chances to rename themselves wi
1493Sounds like a good approach.
1494
1495Kyle - EOSVibes
1496Rob Finch - Cypherglass.com (Block Producer)
1497Happy to do a video. Please send me any details you’d like conveyed.
1498I'm also happy to do a video. Although I think this should be Steemed as an EMLG too.
1499
1500Sharif Bouktila - EOS Dublinadmin
1501The Videos are being recorded and I think should either be released or edited (to remove noise, bad audio etc.. ) and released at a later point.   
1502
1503Personally I don't think I could watch it back,  but I know there is lots of interest.
1504
1505Kyle - EOSVibes
1506Sharif Bouktila - EOS Dublin
1507The Videos are being recorded and I think should either be released or edited (to remove noise, bad audio etc.. ) and released a
1508I meant a video regarding the eosio issuance of tokens to gift the genesis accounts with free ram - that's what was being raised right? Apologies if not, currently catching up on all the Telegram channels - There's like 20 of them! This is becoming a fulltime job in and of iteself!!!
1509
1510Sharif Bouktila - EOS Dublinadmin
1511I hear you!  - EOS FIREHOSE 
1512
1513Personally I don't think the RAM question worth going out with for now.   But others might have a different opinion.
1514
1515Jose Toriello
1516Kyle - EOSVibes
1517I meant a video regarding the eosio issuance of tokens to gift the genesis accounts with free ram - that's what was being raised
1518Yup
1519Sharif Bouktila - EOS Dublin
1520I hear you! - EOS FIREHOSE Personally I don't think the RAM question worth going out with for now. But others might have a
1521Agree. Not worth it. It will only heighten the controversy.
1522
1523David Moss
1524@igorls you here?
1525
1526Igor Lins e Silva - EOS Rio
1527yes
1528
1529Sharif Bouktila - EOS Dublinadmin
1530@DavidMoss
1531
1532Ben Sigman
1533I just popped up this site
1534https://status.producer.vote/
1535
1536EOS Mainnet Status
1537This site shows the daily report from the EOS launch.
1538
1539Sharif Bouktila - EOS Dublinadmin
1540Ben Sigman
1541I just popped up this site
1542You should work in IT ,  nice work!
1543
1544Sukesh Tedla (EOSGreen)
1545Ben Sigman
1546https://status.producer.vote/
1547This is cool. Thanks for your effort.
1548
1549Sharif Bouktila - EOS Dublinadmin
1550Ben Sigman
1551https://status.producer.vote/
1552Hopefully it will be obsolete soon , although would be a nice place for BPs to push performance stats etc...
1553
1554Peter Sveda EOS Germany
1555Sharif Bouktila - EOS Dublin
1556Hopefully it will be obsolete soon , although would be a nice place for BPs to push performance stats etc...
1557:+1:
1558
1559Kyle - EOSVibes
1560Ben Sigman
1561https://status.producer.vote/
1562Helpful. Thanks Ben :+1:
1563Peter Bue | EOSAmericas invited Douglas Horn | EOSAmericas
1564
1565Rob Finch - Cypherglass.com (Block Producer)
1566Kyle - EOSVibes
1567I meant a video regarding the eosio issuance of tokens to gift the genesis accounts with free ram - that's what was being raised
1568The most important thing to convey is that the tokens are basically burned because they’re locked in the system account forever. 
1569
1570If people know that the 12k tokens are a *necessary* step in launching the chain, they will be fine with the decision.
1571
1572Kyle - EOSVibes
1573Rob Finch - Cypherglass.com (Block Producer)
1574The most important thing to convey is that the tokens are basically burned because they’re locked in the system account forever.
1575Then is it even worth conveying?
1576
1577Timothy Lewis
1578But they aren't being burned.
1579So that's not correct information.
1580
1581Sam - EOS Dublin
1582Ben Sigman
1583I just popped up this site
1584Looks great! Although isn't it the 0100 UTC meeting that's the go/no go? The 1300 UTC is an interim status meeting/validation catchup
1585
1586Rob Finch - Cypherglass.com (Block Producer)
1587Kyle - EOSVibes
1588Then is it even worth conveying?
1589Probably not.
1590
1591Timothy Lewis
1592Kyle - EOSVibes
1593I meant a video regarding the eosio issuance of tokens to gift the genesis accounts with free ram - that's what was being raised
1594I think the issue being raised is that the initial supply will be wrong. "If they can't even get the initial supply right, what else is wrong?"
1595
1596mini - EOS Argentina
1597Timothy Lewis
1598I think the issue being raised is that the initial supply will be wrong. "If they can't even get the initial supply right, what
1599We didn't reach consensus on this yesterday?
1600
1601Timothy Lewis
1602That's becuase there was no fix.
1603We are testing a fix. If it fixes, it will be brought up. If it doesn't we are comfortable launching incorrect.
1604
1605Kyle - EOSVibes
160612k are being locked in the System contract forever though right? & There is no way for these EOS to ever be released right?
1607
1608Timothy Lewis
1609it's actually more like 2.0xxxx that will be moved to an unavailable account. It will affect initial RAM costs and BP rewards slightly.
1610It's not a "critical" system issue by any means.
1611It is an optical issue, in my opinion.
1612
1613Sharif Bouktila - EOS Dublinadmin
1614Why not manually add inflation (4%) for Worker Proposals from when the chain was created.  And use that to pay for Ram? 
1615
1616Put the rest into the WP fund.   (We are going to need it)
1617I'm also fine with the create & burn option to be clear.
1618
1619Kyle - EOSVibes
1620I'm pretty sure token holders would rather see an ever-so-slight increase in total token supply than to be charged a RAM fee individually (no matter how small).
1621Yep, send them to a null account when done.
1622
1623Timothy Lewis
1624Kyle - EOSVibes
1625I'm pretty sure token holders would rather see an ever-so-slight increase in total token supply than to be charged a RAM fee ind
1626That was never on the table.
1627Currently the options that I see as fixes are the proposed solution from EOSeoul, the option where wecharge an unclaimed account (with a WP to repay that person... )
1628Actually... Why don't you all just charge one of my accounts and we create a WP to repay me.
1629It's like 20k tokens, right?
1630
1631Sharif Bouktila - EOS Dublinadmin
1632Don't like that , but thanks for the offer.   - Please vote for us 🙂
1633
1634Timothy Lewis
1635I'll do anon
1636
1637Sharif Bouktila - EOS Dublinadmin
1638We'll never get a WP approved for a repay.  We don't even have a Worker Proposal process designed yet.
1639Why not manually add inflation (4%) for Worker Proposals from when the chain was created.  And use that to pay for Ram?
1640Its like 100k per day
1641
1642Kyle - EOSVibes
1643Why not just increase the total supply to the required level and once launched - send the excess to a null account - It's as good as burning them.
1644
1645Timothy Lewis
1646Sharif Bouktila - EOS Dublin
1647Why not manually add inflation (4%) for Worker Proposals from when the chain was created. And use that to pay for Ram?
1648I like this.
1649maybe.
1650let me think.
1651
1652Kyle - EOSVibes
1653Whatever the decision, we should communally Steemit as an EMLG post, maybe along with other info/updates at the time. We can video explain it later if needs be.
1654
1655Timothy Lewis
1656Kyle - EOSVibes
1657Whatever the decision, we should communally Steemit as an EMLG post, maybe along with other info/updates at the time. We can vid
1658+1
1659And the current workaround has blessings from above... So it's not a huge issue. To me its a huge annoyance becuase I think it will be an optics issue.
1660
1661Sharif Bouktila - EOS Dublinadmin
1662Kyle - EOSVibes
1663Whatever the decision, we should communally Steemit as an EMLG post, maybe along with other info/updates at the time. We can vid
1664+1
1665I think we are over thinking this one.  
1666
1667Its not material , lost in the roundings after a couple of days of the chain running.
1668
1669Kyle - EOSVibes
1670@trustlayer Yes
1671Sharif Bouktila - EOS Dublin
1672I think we are over thinking this one. Its not material , lost in the roundings after a couple of days of the chain running.
1673& Yes
1674
1675Kevin Rose - EOS New York
1676Kyle - EOSVibes
1677Whatever the decision, we should communally Steemit as an EMLG post, maybe along with other info/updates at the time. We can vid
1678Agree. Not against @finchify making a video, he’s very good at it. But we need a “faceless” statement as well.
1679
1680Timothy Lewis
1681With a mask and a voice distorter.
1682
1683Sharif Bouktila - EOS Dublinadmin
1684I don't think anyone should make a video until an agreed period after official statements.
1685
1686Timothy Lewis
1687Sharif Bouktila - EOS Dublin
1688I don't think anyone should make a video until an agreed period after official statements.
1689+1
1690
1691Kevin Rose - EOS New York
1692Timothy Lewis
1693With a mask and a voice distorter.
1694I can do a mean Darth Vader.
1695
1696Kyle - EOSVibes
1697Sharif Bouktila - EOS Dublin
1698I don't think anyone should make a video until an agreed period after official statements.
1699+1
1700Current videos around the launch should be light in detail and content at the moment imo. EOS Token Holders are literally hanging off our every word right now.
1701This EMLG community literally amazes me everyday. EOSVibes would be totally honoured if we were to get voted in and work alongside you guys (if). Mucho Respeto!
1702I really hope it stays like this...
1703
1704Sharif Bouktila - EOS Dublinadmin
1705Really is a solid group of people, I'm more and more optimistic each day.
1706But lets stay on topic ... How is the test plans coming along 🙂
1707
1708Ben Sigman
1709Sam - EOS Dublin
1710Looks great! Although isn't it the 0100 UTC meeting that's the go/no go? The 1300 UTC is an interim status meeting/validation ca
1711Yes I can change it up
1712
1713Shaheen Counts - EOS BlockSmith
1714Kevin Rose - EOS New York
1715I can do a mean Darth Vader.
1716I’d like to see this.
1717
1718Kevin Rose - EOS New York
1719Shaheen Counts - EOS BlockSmith
1720I’d like to see this.
1721I'm better at Golem from LOTR. #tulip
1722
1723Sam - EOS Dublin
1724Ben Sigman
1725Yes I can change it up
1726Thanks, the countdown is really helpful as time is just a blur right now 🙂
1727
1728Shaheen Counts - EOS BlockSmith
1729Kevin Rose - EOS New York
1730I'm better at Golem from LOTR. #tulip
1731I do a mean golem myself.   We
1732Might have to have a golem- off at Tulip.
1733
1734Ben Sigman
1735Shaheen Counts - EOS BlockSmith
1736I’d like to see this.
1737Proof of Vader requested by 0100
1738Sam - EOS Dublin
1739Thanks, the countdown is really helpful as time is just a blur right now 🙂
1740Well, I believe that there will be a call tonight
1741But not to vote
1742
1743Branden Espinoza
1744I can do Chewbacca.
1745
1746Timothy Lewis
1747Branden Espinoza
1748I can do Chewbacca.
1749That would be hilarious.
1750With the electronic mask.
1751You'd be perfect for it.
1752(the msg)
1753
1754Shaheen Counts - EOS BlockSmith
1755Branden Espinoza
1756I can do Chewbacca.
1757Haha
1758
1759Branden Espinoza
1760Timothy Lewis
1761(the msg)
1762Oh geeze.
1763I am happy to help however I can. :grin:
1764
1765Kevin Rose - EOS New York
1766Shaheen Counts - EOS BlockSmith
1767I do a mean golem myself. We Might have to have a golem- off at Tulip.
1768I’ll take “Things No One Wants” for $1,000, Alex.
1769
1770Shaheen Counts - EOS BlockSmith
1771Hahaha
1772
1773Sharif Bouktila - EOS Dublinadmin
1774Kevin Rose - EOS New York
1775I’ll take “Things No One Wants” for $1,000, Alex.
1776Thank you @eosnewyork , see you on the other side
1777
1778David P - EOS42
1779Timothy Lewis
1780We are testing a fix. If it fixes, it will be brought up. If it doesn't we are comfortable launching incorrect.
1781Right approach :+1:
1782
1783Josh Kauffman - EOS Canada
1784Nice to see all the arguing has now been focused on who can do a better Golem impression. I think we need EOS Go to be a neutral judge in this though.
1785
1786Sharif Bouktila - EOS Dublinadmin
1787Josh Kauffman - EOS Canada
1788Nice to see all the arguing has now been focused on who can do a better Golem impression. I think we need EOS Go to be a neutral
1789The natural endpoint of all this is a dance off.  
1790
1791I trust Kev and Blue Jays to be neutral in judging.
1792
1793Stuardo Rodríguez 🇬🇹
1794Craig Murray - EOS BlockSmith
1795a new chain is moving backwards unless we find a p0 or p1, we should not start a new chain
1796In case we find a p0 or p1 issue, and we do need to start a new chain, would it be OK to reconsider how to alocate RAM?
1797
1798Roman CryptoLions
1799Sharif Bouktila - EOS Dublin
1800The natural endpoint of all this is a dance off. I trust Kev and Blue Jays to be neutral in judging.
1801zoom call coming up?
1802
1803Nathan Rempel | GenerEOS Sydney
1804in one hour i think
1805
1806Kevin Rose - EOS New York
1807Sharif Bouktila - EOS Dublin
1808The natural endpoint of all this is a dance off. I trust Kev and Blue Jays to be neutral in judging.
1809I should start stretching now then.
1810
1811Marc-Antoine Ross - EOS Canadaadmin
1812Roman CryptoLions
1813zoom call coming up?
1814In one hour yes
1815
1816Nathan Rempel | GenerEOS Sydney
1817I see that eos-mainnet is 80 commits behind eosio
1818
1819Sam - EOS Dublin
1820Roman CryptoLions
1821zoom call coming up?
1822@Bensig created a handy tracker for exactly that! https://status.producer.vote
1823
1824EOS Mainnet Status
1825This site shows the daily report from the EOS launch.
1826Marc-Antoine Ross - EOS Canada invited Celu - Blockgenic
1827Celu - Blockgenic invited Jk (Blockgenic)
1828
1829Peter Bue | EOSAmericas
1830^ I'd also like to confirm the call.
1831
1832Craig Murray - EOS BlockSmith
1833Nathan Rempel | GenerEOS Sydney
1834I see that eos-mainnet is 80 commits behind eosio
1835yes, but I'm not sure it needs to track master.  I suspect they will merge based on new tags and certainly new versioned releases
1836
1837Nathan Rempel | GenerEOS Sydney
1838Craig Murray - EOS BlockSmith
1839yes, but I'm not sure it needs to track master. I suspect they will merge based on new tags and certainly new versioned release
1840Fair enough
1841
1842Andrey Marchuk
1843and David confirmed on the morning call that there are no critical fixes to worry about
1844
1845Marc-Antoine Ross - EOS Canadaadmin
1846All,
1847
1848Here's the proposed agenda:
1849Security report update - Dafeng EOS Asia
1850ABP selection update - Kevin EOS New York
1851go / no go
1852Ben from shEOS asks: How can we insure that voting portals are handling private keys well?
1853    Create a sub-team to prepare recommendations?
1854
1855https://zoom.us/j/885770550
1856
1857Zoom Video
1858Join our Cloud HD Video Meeting now
1859Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
1860Marc-Antoine Ross - EOS Canada pinned « All, Here's the proposed agenda: Security report update - Dafeng EOS Asia ABP selection update - Kevin EOS New York go / no go »
1861
1862Timothy Lewis
1863Marc-Antoine Ross - EOS Canada
1864All, Here's the proposed agenda: Security report update - Dafeng EOS Asia ABP selection update - Kevin EOS New York go / no go
1865Time?
1866
1867David Moss
18686pm
1869
1870Marc-Antoine Ross - EOS Canadaadmin
1871Now!
1872Timothy Lewis
1873Time?
1874It's always 0100UTC and 1300UTC until further notice
1875
1876Craig Murray - EOS BlockSmith
1877Marc-Antoine Ross - EOS Canada
1878It's always 0100UTC and 1300UTC until further notice
1879FOREVER!
1880
1881Timothy Lewis
1882🙂
1883
1884Bo - EOS Silicon Valley
1885 191 KB
1886 
1887James Sutherland - Cypherglass.com
1888 702 KB
1889 
1890Andrey Marchuk
1891thanks
1892
1893James Sutherland - Cypherglass.com
1894Google mangled it, but it's somewhat readable
1895
1896Nathan Rempel | GenerEOS Sydney
1897the github translates pretty well
1898
1899Devin Lee KOREOS.IO
1900James Sutherland - Cypherglass.com
1901English_Auto_Translation_超级节点安全审计方案初稿.pdf
1902Already reported by securty firm?
1903
1904James Sutherland - Cypherglass.com
1905Preliminary, just 3 pages.  More to come
1906
1907Devin Lee KOREOS.IO
1908James Sutherland - Cypherglass.com
1909Preliminary, just 3 pages. More to come
1910Thanks.
1911
1912Craig Murray - EOS BlockSmith
1913another highly productive and this time extremely effecient meeting, thanks everyone!
1914
1915Nathan Rempel | GenerEOS Sydney
1916Timothy Lewis
1917Updated: https://gist.github.com/redjade/bdbcb10708e165b29d0301c5defa1d83
1918Have you been able to successfully execute these changes using the boot bios? I'm working on a similar fix now (not because i think it's needed, but just as a test) but day job conflicts
1919Craig Murray - EOS BlockSmith
1920another highly productive and this time extremely effecient meeting, thanks everyone!
1921Yes agreed
1922@marcantoineross If i can propose an item for next meetings agenda, review the current state of the UAT. Are people supplying proof of tests, adding tests, running tests
1923
1924Timothy Lewis
1925Nathan Rempel | GenerEOS Sydney
1926Have you been able to successfully execute these changes using the boot bios? I'm working on a similar fix now (not because i th
1927I'll DM you. May not fully solve the entire issue.
1928
1929Nathan Rempel | GenerEOS Sydney
1930Timothy Lewis
1931I'll DM you. May not fully solve the entire issue.
1932:+1:
1933
1934Tim Weston - GenerEOS (BP Sydney)
1935Hey guys, did we get a channel created to discus the voting portal etc ?
1936If not I’m happy to throw one up
1937
1938Marc-Antoine Ross - EOS Canadaadmin
1939All, 
1940
1941Thanks for another productive call!
1942
1943Find bellow the minutes, if you find anything not accurate, please suggest/comment and we will fix.
1944The raw log is included at the bottom of the document.
1945
1946https://docs.google.com/document/d/1HR16WF5nhNXNzkBh963ZKjSflsyBsMb0PsOhHSbQTsI
1947
1948Next steps June 7, 1300 UTC:
1949    Security report update - Dafeng EOS Asia
1950    ABP selection update - Kevin EOS New York
1951    Follow-up constitution 
1952    Review the current state of the UAT testing. Are people supplying proof of tests, adding tests, running tests
1953    More?
1954
1955Thanks, good after-mor-night!
1956
1957Google Docs
1958Go/NoGo June 7 0100 UTC
1959Go/NoGo June 7 0100 UTC Note: For internal use only for the EOS Validation (EMLG) Telegram Channel. Please do not share outside of this channel. 100...
1960Marc-Antoine Ross - EOS Canada pinned « All, Thanks for another productive call! Find bellow the minutes, if you find anything not accurate, please suggest/comment a»
1961Jk (Blockgenic)
1962Tim Weston - GenerEOS (BP Sydney)
1963Hey guys, did we get a channel created to discus the voting portal etc ?
1964Let me know if you do.
1965
1966Zhao Yu@ EOSLaoMao.com
1967and the group?
1968
1969Nathan Rempel | GenerEOS Sydney
1970Tim has to up his Telegram game 🤣
1971
1972Branden Espinoza
1973Tim, you ceated a channel, not a group.  That is for 1 way comms only.
1974
1975Tim Weston - GenerEOS (BP Sydney)
1976whoops will create now
1977
1978Nathan Rempel | GenerEOS Sydney
1979https://t.me/joinchat/IbfNrxA6yqKbzBXSXZxteA
1980
1981Tim Weston - GenerEOS (BP Sydney)
1982:point_up_2:🏻:point_up_2:🏻 here it is guys!
1983
1984Nathan Rempel | GenerEOS Sydney
1985Some fun messages from @daniellarimer
1986
1987Nathan Rempel | GenerEOS Sydney
1988Daniel LarimerJun 6, 2018 11:12:40 PM
1989I like how serious everyone is, but perfection is enemy of good enough
1990No, we wil run and live!
1991William Wallace: Yes!, Fight and you may die. Run and you will live at least awhile. And dying in your bed many years from now, would you be willing to trade all the days from this day to that for one chance, just one cahnce, to come back here as young men and tell our enemies that they may take our lives but they will never take our freedom!!!
1992I see people petrified by fear of unknown bugs. Life is messy. Be brave. We can overcome anything
1993Fortune favors the bold. And voters will notice.
1994I cannot promise you there will be no bugs or no losses. But each day people lose money to scams and new risks Mount.   The rag tag teams of producers on steem and bitshares can do this.   Surely the professionals here can.
1995
1996Kyunghwan Kim - EOSeoul.io
1997Timothy Lewis
1998We are testing a fix. If it fixes, it will be brought up. If it doesn't we are comfortable launching incorrect.
1999Thank you! :+1:
2000
2001Ben Sigman
2002[Photo]
2003
2004Matthew Darwin - EOS Nation
2005Marc-Antoine Ross - EOS Canada
2006All, Thanks for another productive call! Find bellow the minutes, if you find anything not accurate, please suggest/comment a
2007Marc, thanks for the great notes!
2008
2009Roshan - EOS Authority
2010Marc-Antoine Ross - EOS Canada
2011All, Thanks for another productive call! Find bellow the minutes, if you find anything not accurate, please suggest/comment a
2012Thanks for the notes!
2013
2014Sandwich
2015Nathan Rempel | GenerEOS Sydney
2016I like how serious everyone is, but perfection is enemy of good enough
2017:fire:
2018Denis | EOS Nation invited Yves La Rose - EOS Nation
2019
2020Roman CryptoLions
2021Sam - EOS Dublin
2022@Bensig created a handy tracker for exactly that! https://status.producer.vote
2023nice
2024
2025Sharif Bouktila - EOS Dublinadmin
2026Next Validation Call is in 35 minutes 
2027
2028
2029 Security report update - Dafeng EOS Asia
2030 ABP selection update - Kevin EOS New York
2031 Follow-up constitution 
2032 Review the current state of the UAT testing. Are people supplying proof of tests, adding tests, running tests
2033 More?
2034
2035Either @marcantoineross or I will post Zoom link 5 minutes before call.
2036
2037Tim Weston - GenerEOS (BP Sydney)
2038:+1:
2039
2040Marc-Antoine Ross - EOS Canadaadmin
2041All,
2042
2043Here's the proposed agenda:
2044    Security report update - Dafeng EOS Asia
2045    ABP selection update - Kevin EOS New York
2046    Follow-up constitution 
2047    Review the current state of the UAT testing. Are people supplying proof of tests, adding tests, running tests
2048    More?
2049
2050https://zoom.us/j/438337388
2051
2052Zoom Video
2053Join our Cloud HD Video Meeting now
2054Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
2055Marc-Antoine Ross - EOS Canada pinned « All, Here's the proposed agenda: Security report update - Dafeng EOS Asia ABP selection update - Kevin EOS New York »
2056
2057Thomas "Disclaimer" Cox (all opinions mine)
2058Marc-Antoine Ross - EOS Canada
2059All, Here's the proposed agenda: Security report update - Dafeng EOS Asia ABP selection update - Kevin EOS New York
2060Reword "Follow-up constitution" to "follow-up on Constitution Article 9 Rollback Proposal" please?
2061
2062Marc-Antoine Ross - EOS Canadaadmin
2063done in the zoom chat
2064Marc-Antoine Ross - EOS Canada invited Miłosz Eos Emerge - Poland
2065
2066Brett Jeffery @ EOS the World
2067Nathan Rempel | GenerEOS Sydney
2068I like how serious everyone is, but perfection is enemy of good enough
2069:+1:
2070Elliot@EOS Pacific invited jason wang
2071
2072Nathan Rempel | GenerEOS Sydney
2073https://docs.google.com/spreadsheets/d/1gJnn0KS4rgDnTowPlN80gulVI77lRgldPhH17kZOnnI
2074
2075Google Docs
2076EOS Voting Portal Audit
2077About
2078
2079This spreadsheet is a list compiled by members of the EOS community( EMLG)
2080It is a list of all known EOS voting portals
2081This list is compile...
2082https://t.me/joinchat/IbfNrxA6yqKbzBXSXZxteA
2083
2084Kyunghwan Kim - EOSeoul.io
2085Timothy Lewis
2086We are testing a fix. If it fixes, it will be brought up. If it doesn't we are comfortable launching incorrect.
2087Being late, but finally got tested version of contracts for adjusting 1) token supply, 2) balance of system accounts, and 3) bancor state.
2088
2089https://github.com/eoseoul/eos-ramcost
2090
2091GitHub
2092eoseoul/eos-ramcost
2093eos-ramcost - Adjusting supply of a token and connector balance of bancor during final phase of boot.
2094
2095Nathan Rempel | GenerEOS Sydney
2096looks good to me, nice and clean. we''ll need this tested in boot sequence asap (12 hours)
2097
2098Alexandre Bourget - EOS Canada
2099Kyunghwan Kim - EOSeoul.io
2100Being late, but finally got tested version of contracts for adjusting 1) token supply, 2) balance of system accounts, and 3) ban
2101There is a problem with the .abi files.. if at any time the ABI files do not contain all the methods from all the contracts that take place in the eosio account.. we will have problems fetching those blocks.
2102
2103Nathan Rempel | GenerEOS Sydney
2104i looked at the cpps :(
2105Alexandre Bourget - EOS Canada
2106There is a problem with the .abi files.. if at any time the ABI files do not contain all the methods from all the contracts that
2107good catch
2108
2109Alexandre Bourget - EOS Canada
2110That was already voted on though..
2111
2112Nathan Rempel | GenerEOS Sydney
2113ok, i'll shelf it
2114
2115Thomas "Disclaimer" Cox (all opinions mine)
2116Strongly encourage all BPs who have done testing, to log their tests here:
2117
2118https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit#gid=1501553294
2119
2120Google Docs
2121EOS UAT - User Acceptance Testing
2122Home
2123
2124
2125Create a Case, Record a Test
2126Procedure 1: Create a Case
2127STEPS
21281, Confirm your case does not yet exist
2129a, Click the red Cases tab at the bo...
2130
2131Kyunghwan Kim - EOSeoul.io
2132Alexandre Bourget - EOS Canada
2133There is a problem with the .abi files.. if at any time the ABI files do not contain all the methods from all the contracts that
2134All actions in eosio.system.ramcost and eosio.token.ramcost are implemented there. Am I right in thinking that you mean that after replacing to original contracts  removed actions cause problems?
2135
2136Ben Sigman
2137Alexandre Bourget - EOS Canada
2138That was already voted on though..
2139As I understand, there were no viable alternatives. Now that there is, don’t we want to offer it to the community?
2140
2141Kyunghwan Kim - EOSeoul.io
2142Alexandre Bourget - EOS Canada
2143There is a problem with the .abi files.. if at any time the ABI files do not contain all the methods from all the contracts that
2144If there is missing function in eosio.system.ramcost and eosio.token.ramcost with respective abi files, please tell me. It would be quite helpful.
2145
2146Alexandre Bourget - EOS Canada
2147This proposition is quite complex (technically for code review, boot_seq adjustements, validation tools adjustments, and socially for getting agreement), seeking to adjust a 1/10 of a day's inflation fluctuation.
2148
2149I wouldn't go to war for this.
2150
2151Nathan Rempel | GenerEOS Sydney
2152Alexandre Bourget - EOS Canada
2153This proposition is quite complex (technically for code review, boot_seq adjustements, validation tools adjustments, and sociall
2154Concur at this stage
2155
2156Mr Fox
2157so， who can give a summary about what to do tomorrow?
2158thanks
2159
2160Kyunghwan Kim - EOSeoul.io
2161Okay. eos-ramcost is fully tested in my local environment. That is to explain and present tools that people requested and to get feedbacks. I have no intention to argue.
2162
2163Nathan Rempel | GenerEOS Sydney
2164Mr Fox
2165so， who can give a summary about what to do tomorrow?
2166instructions will be available pending the result of the go / no meeting
2167Kyunghwan Kim - EOSeoul.io
2168Okay. eos-ramcost is fully tested in my local environment. That is to explain and present tools that people requested and to get
2169I think it's fantastic work, the timing is just difficult
2170
2171Kyunghwan Kim - EOSeoul.io
2172Nathan Rempel | GenerEOS Sydney
2173I think it's fantastic work, the timing is just difficult
2174I have same opinion with you. :)
2175
2176Nathan Rempel | GenerEOS Sydney
2177I think anyone helping to solve issues for the launch and the community should be commended
2178
2179Mr Fox
2180Nathan Rempel | GenerEOS Sydney
2181instructions will be available pending the result of the go / no meeting
2182thanks
2183
2184deck - EOS New York
2185Everyone. I am treating the 4th criteria from the spreadsheet to mean that you need to send an overview of your security/tech specs to me (please keep it to 3-4 sentences. I do not believe we have time for me or someone else to do a full security audit. Is that sufficient for everyone?
2186https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=753803902
2187
2188Google Docs
2189EOS Mainnet Validation Plan
2190Validation Tools
2191
2192Name, Scope of Tests, BPs who will execute, How Long for Execution?
2193Firestarter from EOS Argentina, Injects csv, tool agnostic, sy...
2194
2195Sharif Bouktila - EOS Dublinadmin
2196deck - EOS New York
2197Everyone. I am treating the 4th criteria from the spreadsheet to mean that you need to send an overview of your security/tech sp
2198Yes
2199
2200Nathan Rempel | GenerEOS Sydney
2201deck - EOS New York
2202Everyone. I am treating the 4th criteria from the spreadsheet to mean that you need to send an overview of your security/tech sp
2203Fine for us
2204
2205Nate D - Aloha EOS
2206deck - EOS New York
2207Everyone. I am treating the 4th criteria from the spreadsheet to mean that you need to send an overview of your security/tech sp
2208:+1:
2209Miłosz Eos Emerge - Poland invited Krzysztof Manijak - EOSEmerge.io - Poland
2210
2211Timothy Lewis
2212Kyunghwan Kim - EOSeoul.io
2213Being late, but finally got tested version of contracts for adjusting 1) token supply, 2) balance of system accounts, and 3) ban
2214Awesome. @jemxpat @jaechung
2215Kyunghwan Kim - EOSeoul.io
2216Okay. eos-ramcost is fully tested in my local environment. That is to explain and present tools that people requested and to get
2217This was really well done. I commend you for the effort, regardless of outcome.
2218
2219David Moss
2220+1
2221
2222Marc-Antoine Ross - EOS Canadaadmin
2223All, 
2224
2225Thanks for an amazing call!
2226
2227Find bellow the minutes, if you find anything not accurate, please suggest/comment and we will fix.
2228The todo for next call is included in the minutes
2229The raw log is included at the bottom of the document.
2230
2231https://docs.google.com/document/d/1Fpevju50lpXDH50dMH0A4NOUnUioHb7xYy76RQXG1w4
2232
2233Next call June 8, 0100 UTC
2234
2235Thanks, good after-mor-night!
2236
2237Google Docs
2238Validation Call June 7 1300 UTC
2239Validation Call June 7 1300 UTC Note: For internal use only for the EOS Validation (EMLG) Telegram Channel. Please do not share outside of this chann...
2240Marc-Antoine Ross - EOS Canada pinned « All, Thanks for an amazing call! Find bellow the minutes, if you find anything not accurate, please suggest/comment and we wi»
2241
2242David Moss
2243Marc-Antoine Ross - EOS Canada
2244All, Thanks for an amazing call! Find bellow the minutes, if you find anything not accurate, please suggest/comment and we wi
2245Thanks @marcantoineross and team!
2246
2247Jose Toriello
2248Someone leaked minutes...
2249
2250Jose Toriello
2251Eduardo CuevasJun 7, 2018 11:10:25 AM
2252https://www.trustnodes.com/2018/06/06/eos-launch-delayed-pending-audit-results
2253
2254Trustnodes
2255EOS Launch Delayed Pending Audit Results
2256A closed door online meeting of block producers has delayed the launch of EOS following the recent disclosure of a number of protocol bugs. After 48 hours of testing, the...
2257
2258Nathan Rempel | GenerEOS Sydney
2259neat we can reverse blocks at will
2260apparently
2261
2262Craig Murray - EOS BlockSmith
2263@eosnewyork is one of the questions we're asking the abp candidates to provide "what method of injection are you using and is it publicly available" ?   It's not yet clear to me how the thing is going to be set up.  This is just up to the abp's discretion to make something himself or using something pubicly available?
2264@DavidMoss perhaps you have comment on this as well?
2265
2266Nathan Rempel | GenerEOS Sydney
2267Craig Murray - EOS BlockSmith
2268@eosnewyork is one of the questions we're asking the abp candidates to provide "what method of injection are you using and is it
2269don't think its possible for @eosnewyork to make a decision based on boot method
2270
2271Kevin Rose - EOS New York
2272Craig Murray - EOS BlockSmith
2273@eosnewyork is one of the questions we're asking the abp candidates to provide "what method of injection are you using and is it
2274I have shoddy service. On a plane.  Enter any criteria you think is valuable into the google doc. We will go through to create a final list. David Moss will gave input and it will be pushed back out to the community.
2275
2276Nathan Rempel | GenerEOS Sydney
2277as long as the chain is validated it could be hand bombed i think
2278
2279Craig Murray - EOS BlockSmith
2280we've argued about ram for a while now, do we even know what method one of these 16 people will use?
2281
2282Kevin Rose - EOS New York
2283Craig Murray - EOS BlockSmith
2284we've argued about ram for a while now, do we even know what method one of these 16 people will use?
2285I don’t think that is up to the ABP.
2286Have we tested JEMs RAM option that rounds to a perfect 1BB?
2287
2288Michael Yeates
2289we have that on our chain now
2290
2291Craig Murray - EOS BlockSmith
2292what is the github link?
2293
2294Michael Yeates
2295to our chain?
2296
2297Craig Murray - EOS BlockSmith
2298to the tool used to inject it, JEM's option
2299
2300Michael Yeates
2301ill get it for you
2302
2303Kevin Rose - EOS New York
2304We have until 1600 UTC to input ABP required criteria.
2305I don’t want this process to hold up a go/no-go decision at 0100
2306
2307Jae Chung - HKEOS
2308Craig Murray - EOS BlockSmith
2309to the tool used to inject it, JEM's option
2310https://github.com/HKEOS/Ghostbusters-Testnet/tree/master/chain-validator
2311was sent ~3 days ago
2312
2313GitHub
2314HKEOS/Ghostbusters-Testnet
2315Ghostbusters-Testnet - EOS Core- an EOS mainnet launch solution
2316
2317Craig Murray - EOS BlockSmith
2318it's like 90% of what the ABP does... the other 10% staying alive... and there has been heaps of fighting about ram solutions, just leaving it up to the abp chosen seems like a good way to continue combat, and also for the selected abp to have to deal with things while remaining anon
2319
2320Kevin Rose - EOS New York
2321Craig Murray - EOS BlockSmith
2322it's like 90% of what the ABP does... the other 10% staying alive... and there has been heaps of fighting about ram solutions, j
2323Like I said, I think that any ABP that is applying for this position is consenting to the community approved process.
2324
2325Craig Murray - EOS BlockSmith
2326Kevin Rose - EOS New York
2327Like I said, I think that any ABP that is applying for this position is consenting to the community approved process.
2328then we need a community approved process pretty quick!
2329
2330Kevin Rose - EOS New York
2331Put what you want into the criteria list. The best way to solicit consensus is when that list is final and pushed back out to the community at 1600 UTC.
2332
2333Craig Murray - EOS BlockSmith
233416 candidates, i really like everyone's entheusiasm.  Personally I think there is a very short list of people that should be doing this.  If the anon ABP does not get a valid chain the first try, it undermines this entire process and sets us back.   Do we let them try again, or choose another person?
2335
2336Sheldon | EOShenzhen
2337Jae Chung - HKEOS
2338https://github.com/HKEOS/Ghostbusters-Testnet/tree/master/chain-validator was sent ~3 days ago
2339this is really awesome
2340
2341Craig Murray - EOS BlockSmith
2342Kevin Rose - EOS New York
2343Put what you want into the criteria list. The best way to solicit consensus is when that list is final and pushed back out to th
2344I have added criteria
2345
2346Kevin Rose - EOS New York
2347Craig Murray - EOS BlockSmith
234816 candidates, i really like everyone's entheusiasm. Personally I think there is a very short list of people that should be doi
2349If they fail I propose we go back to the list of applicants. But that’s just my opinion.
2350
2351Craig Murray - EOS BlockSmith
2352Jae Chung - HKEOS
2353https://github.com/HKEOS/Ghostbusters-Testnet/tree/master/chain-validator was sent ~3 days ago
2354thx
2355
2356Alex - EOS SOCAL
2357Kevin Rose - EOS New York
2358If they fail I propose we go back to the list of applicants. But that’s just my opinion.
2359Agreed
2360
2361Craig Murray - EOS BlockSmith
2362well there is a bit of an elephant in the room, so I'm just trying to shine some light on it.  Who does the injection and how it's done has been a massive fighting point
2363i recommend we figure that out before the abp is chosen
2364
2365Sukesh Tedla (EOSGreen)
2366Where can one find the list of ABP candidates? I cannot find that in the document, should we add it to the doc?
2367
2368Kevin Rose - EOS New York
2369Sukesh Tedla (EOSGreen)
2370Where can one find the list of ABP candidates? I cannot find that in the document, should we add it to the doc?
2371It is secret to avoid security risks and merchandizing the responsibility to the token holders.
2372Eric_EOSARMY.io invited phajek eosarmy Patrick
2373
2374Kevin Rose - EOS New York
2375The BPCs present on the previous 1300 UTC asked that EOS New York field and manage the list with David Moss as a witness.
2376Miłosz Eos Emerge - Poland invited Marek EOSEmerge.io - Poland
2377
2378Nate D - Aloha EOS
2379Craig Murray - EOS BlockSmith
2380well there is a bit of an elephant in the room, so I'm just trying to shine some light on it. Who does the injection and how it
2381I don't think the how matters, as long as the data state matches what everyone expects and tests pass.
2382
2383Craig Murray - EOS BlockSmith
2384Nate D - Aloha EOS
2385I don't think the how matters, as long as the data state matches what everyone expects and tests pass.
2386so we leave it up to the abp to decide then?
2387Sukesh Tedla (EOSGreen)
2388Where can one find the list of ABP candidates? I cannot find that in the document, should we add it to the doc?
2389we have suspended radical transparency and the list is hidden, as will be the name of the anon abp
2390
2391Sukesh Tedla (EOSGreen)
2392Kevin Rose - EOS New York
2393The BPCs present on the previous 1300 UTC asked that EOS New York field and manage the list with David Moss as a witness.
2394Sorry! I wasn't able to join the meeting. I don't know what was discussed but we wanted to go with the consensus decision.
2395
2396Nate D - Aloha EOS
2397Craig Murray - EOS BlockSmith
2398so we leave it up to the abp to decide then?
2399The process they use to boot? Yes, I think so.
2400
2401Craig Murray - EOS BlockSmith
2402the tool they used to inject the snapshot, purchase the ram, setup the b1 account, resign the eosio account, validate the steps taken, and im sure there are other things.  The method used will affect the result and we then validate that... but we dont have consensus on the method of doing such, so how can we validate?  This has been a major point of contention, that's my broader point.  But not figuring out what we plan to do, either choose a method, leave it up to the abp, whatever, we need to make sure everyone is happy because it could lead to lack on consensus on validity.  Not to mention it would be nice to be testing the various tools these groups might use to make sure they work so the abp isn't stuck being anon with a broken tool
2403
2404Nate D - Aloha EOS
2405We already voted on how to handle the ram purchase and tokens, so I would expect the ABP to stick to that unless we vote again to change it.
2406
2407Sukesh Tedla (EOSGreen)
2408Nate D - Aloha EOS
2409We already voted on how to handle the ram purchase and tokens, so I would expect the ABP to stick to that unless we vote again t
2410+1
2411
2412Craig Murray - EOS BlockSmith
2413there are 2 tools that I know of, Igor has one that uses eosjs.  Alex has one that uses golang.
2414Nate D - Aloha EOS
2415We already voted on how to handle the ram purchase and tokens, so I would expect the ABP to stick to that unless we vote again t
2416did we?  I'm sorry I'm trying to catch up on the details i missed some of the meeting
2417and this method is currently expressed in Igor's repo that was linked earlier?
2418
2419Nate D - Aloha EOS
2420Craig Murray - EOS BlockSmith
2421did we? I'm sorry I'm trying to catch up on the details i missed some of the meeting
2422Yes, I'd have to dig up when exactly but it was 2-3 meetings ago.
2423
2424Craig Murray - EOS BlockSmith
2425Jae Chung - HKEOS
2426https://github.com/HKEOS/Ghostbusters-Testnet/tree/master/chain-validator was sent ~3 days ago
2427forgive me if i'm missing the obvious, trying to quickly review this code.  I don't see the b.1 account setup in that code.  Am I missing it?
2428Nate D - Aloha EOS
2429Yes, I'd have to dig up when exactly but it was 2-3 meetings ago.
2430I'm pretty sure we did not have consensus on a ram buying method 2-3 meetings ago.  I haven't missed a meeting yet until this morning and people have been debating it more recently
2431but please if you have minutes that would be great, i would be thrilled if this was actually already resolved
2432
2433Nate D - Aloha EOS
2434Yeah I'm looking...
2435https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c/edit
2436
2437Google Docs
2438GoNoGo Call
2439Wednesday 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, E...
2440
2441Kevin Rose - EOS New York
2442Can someone share the testing doc with with Dan Larimer?
2443
2444Craig Murray - EOS BlockSmith
2445https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=668547189
2446
2447Google Docs
2448EOS Mainnet Validation Plan
2449Validation Tools
2450
2451Name, Scope of Tests, BPs who will execute, How Long for Execution?
2452Firestarter from EOS Argentina, Injects csv, tool agnostic, sy...
2453i've sent him that one, i think there is also another one
2454
2455Kevin Rose - EOS New York
2456Craig Murray - EOS BlockSmith
2457i've sent him that one, i think there is also another one
2458Thank you
2459
2460Craig Murray - EOS BlockSmith
2461there is also Thomas's one, but i honestly haven't had time to look at it, i dont have a link handy
2462
2463Josh Kauffman - EOS Canada
2464https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit#gid=1501553294
2465
2466Google Docs
2467EOS UAT - User Acceptance Testing
2468Home
2469
2470
2471Create a Case, Record a Test
2472Procedure 1: Create a Case
2473STEPS
24741, Confirm your case does not yet exist
2475a, Click the red Cases tab at the bo...
2476^^ Daniel
2477Craig Murray - EOS BlockSmith
2478I'm pretty sure we did not have consensus on a ram buying method 2-3 meetings ago. I haven't missed a meeting yet until this mo
2479On a previous call, there was a vote for this and it was chosen that creating the extra EOS made the most sense and the ABP should go with that.
2480
2481Craig Murray - EOS BlockSmith
2482Ok so @jemxpat is ok with this?  @jaechung and @michaelyeates and @igorls and @xebb82 and @trustlayer are all ok with this?
2483to be clear i do not care at all what method is used I'm just trying to avoid conflict after an abp is chosen
2484
2485Michael Yeates
2486please can we put this on the agenda for the next meeting
2487
2488Marc-Antoine Ross - EOS Canadaadmin
2489How the chain is booted does not matter as much as validation of its content.
2490
2491We have consensus on the content of the chain, as per the minutes. Look for "Question (21:50:00)" and the notes following.
2492https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c
2493
2494Google Docs
2495GoNoGo Call
2496Wednesday 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, E...
2497
2498Craig Murray - EOS BlockSmith
2499ok.  To be clear, my understanding is now that we have consensus that eos.io should issue an extra approx 19k tokens and they be used to fund the accounts.  This means a chain which does not do so is invalid?
2500
2501Marc-Antoine Ross - EOS Canadaadmin
2502Craig Murray - EOS BlockSmith
2503ok. To be clear, my understanding is now that we have consensus that eos.io should issue an extra approx 19k tokens and they be
2504Correct
2505
2506Yves La Rose - EOS Nation
2507This was the consensus yesterday, yes.
2508
2509Timothy Lewis
2510Craig Murray - EOS BlockSmith
2511@eosnewyork is one of the questions we're asking the abp candidates to provide "what method of injection are you using and is it
2512I like this.
2513Craig Murray - EOS BlockSmith
2514ok. To be clear, my understanding is now that we have consensus that eos.io should issue an extra approx 19k tokens and they be
2515If a solution is found and presented, it may be considered. I do not know if we could reach consensus on the change, but @resvera has created a working, tested solution. It needs to be further audited, but it appears to be ready to go.
2516
2517Craig Murray - EOS BlockSmith
2518Timothy Lewis
2519If a solution is found and presented, it may be considered. I do not know if we could reach consensus on the change, but @resver
2520Per the previous information it is not considered a problem, and any solution would result in an invalid chain.  But I understand this is not a unanimous opinion which is why I'm trying to draw out this debate now, before an abp is selected.  I do not want someone spinning up a chain without 19k extra eos and having that be an invalid chain because it does not respect the rule imposed by the vote outlined previously
2521
2522mini - EOS Argentina
2523Timothy Lewis
2524If a solution is found and presented, it may be considered. I do not know if we could reach consensus on the change, but @resver
2525We can't keep delaying things if we already reach consensus. Yes, it would be nice to not send extra tokens to an account with a invalid key to "burn " them. but we reach consensus  :) 
2526
2527We should delay thing only for critical things. Otherwise we are in an infinite loop reaching for perfection
2528
2529Sharif Bouktila - EOS Dublinadmin
2530We know how to validate the chain using a variety of tools. 
2531
2532Let @eosnewyork and @DavidMoss figure it out.
2533
2534If that chain gets to 15% we are in business.  If not we start again.
2535
2536Denis | EOS Nation
2537Daniel LarimerJun 7, 2018 12:11:55 PM
2538We are preparing a 1.0.2 update that will fix things with the optional whitelist/blacklist for contracts
2539
2540Craig Murray - EOS BlockSmith
2541Sharif Bouktila - EOS Dublin
2542We know how to validate the chain using a variety of tools. Let @eosnewyork and @DavidMoss figure it out. If that chain gets
2543we are about to validate another chain, we cannot rely on NY and David to figure that out.  We must have overwhelming consensus that we are valid and right now I do not know if we can achieve that based on disputes about RAM purchasing methods
2544Denis | EOS Nation
2545We are preparing a 1.0.2 update that will fix things with the optional whitelist/blacklist for contracts
2546yup, and then there's that to add to the mix :smile:
2547this is why i'm pressing this issue because it needs resolved quickly so that it does not disrupt our existing timelines.  more delays are not in our best interest
2548
2549Sharif Bouktila - EOS Dublinadmin
2550Ok - We have a process , I suggest we put it on the agenda at 01:00 UTC 
2551
2552@jemxpat @michaelyeates @trustlayer @abourget @marcantoineross 
2553
2554I propose result of next vote is set in stone.  
2555
2556Agreed?
2557
2558Craig Murray - EOS BlockSmith
2559i think the last one is set in stone... im just trying to get those who do not agree that it is in stone to speak up
2560
2561Sharif Bouktila - EOS Dublinadmin
2562Reason why , is the first time it was voted it was the first call we did that type of decision making, on something this decisive I think it’s ok to revisit
2563
2564Jae Chung - HKEOS
2565@abourget you were explaining the math for minimum difference in head block and LIB with 21 producers earlier. Could you forward the message from Bart or copy&paste that here again?
2566
2567Sharif Bouktila - EOS Dublinadmin
2568We are starting a new chain anyway aren’t we?
2569
2570Jae Chung - HKEOS
2571this is something important for all of us to know for mainnet— it means minimum catch up time for LIB is ~3 minutes
2572
2573Denis | EOS Nation
2574Craig Murray - EOS BlockSmith
2575yup, and then there's that to add to the mix :smile:
2576Since we are already doing a reset on the chain, it might be something to consider.
2577
2578I have no preference, 1.0.1 or 1.0.2 is fine with me (preference to 1.0.2 if we have concensus)
2579
2580Jae Chung - HKEOS
2581Denis | EOS Nation
2582Since we are already doing a reset on the chain, it might be something to consider. I have no preference, 1.0.1 or 1.0.2 is fin
2583so you do have a preference ;)
2584
2585Denis | EOS Nation
2586Sharif Bouktila - EOS Dublin
2587We are starting a new chain anyway aren’t we?
2588Yes, new chain is required because of constitution changes (for legal reasons)
2589Jae Chung - HKEOS
2590so you do have a preference ;)
2591I vote :+1: for both
2592
2593mini - EOS Argentina
259421*12*2/3
2595@jaechung
2596
2597Denis | EOS Nation
2598Jae Chung - HKEOS
2599so you do have a preference ;)
2600It's a patch update, no feature changes, so it shouldn't be an issue if we do or do not use it
2601
2602Sharif Bouktila - EOS Dublinadmin
2603Denis | EOS Nation
2604Yes, new chain is required because of constitution changes (for legal reasons)
2605I agree we should,  but don’t quite understand that as we will be able to change constitution later.
2606
2607Denis | EOS Nation
2608Jae Chung - HKEOS
2609so you do have a preference ;)
2610Jae, do you have time to look into it? I'll support your judgement
2611
2612Jae Chung - HKEOS
2613Denis | EOS Nation
2614Jae, do you have time to look into it? I'll support your judgement
2615yep, we're looking into it now but at the moment I agree with you— preference for 1.0.2
2616
2617Craig Murray - EOS BlockSmith
2618Sharif Bouktila - EOS Dublin
2619I agree we should, but don’t quite understand that as we will be able to change constitution later.
2620only before 15%, and even then it's a little sketchy... we're validating the chain, everything.  Once that's done it can't change until 15% and voter ref
2621
2622Sharif Bouktila - EOS Dublinadmin
2623Craig Murray - EOS BlockSmith
2624only before 15%, and even then it's a little sketchy... we're validating the chain, everything. Once that's done it can't chang
2625Thanks
2626
2627Denis | EOS Nation
2628Sharif Bouktila - EOS Dublin
2629I agree we should, but don’t quite understand that as we will be able to change constitution later.
2630We are recompiling the eosio.system ABI, this needs to be loaded in the initial boot sequence.
2631
2632Craig Murray - EOS BlockSmith
2633if we're doing a new chain, 1.0.2 yes :+1:
2634
2635Denis | EOS Nation
2636Jae Chung - HKEOS
2637yep, we're looking into it now but at the moment I agree with you— preference for 1.0.2
2638:+1: perfect
2639
2640Jae Chung - HKEOS
2641mini - EOS Argentina
264221*12*2/3
2643Thanks. On the acceptance testing chain the LIB is ~325 blocks behind head block num— so I'm assuming this is what we'll have on mainnet :confused:
2644
2645mini - EOS Argentina
2646Yes shouldn't be 325, don't know if has anything to do with the boot process.
2647Or a bug :/
2648
2649Craig Murray - EOS BlockSmith
2650Jae Chung - HKEOS
2651Thanks. On the acceptance testing chain the LIB is ~325 blocks behind head block num— so I'm assuming this is what we'll have on
2652yes Dan confirmed normal operation was that, or higher
2653
2654Thomas "Disclaimer" Cox (all opinions mine)
2655FYI, I'm still finishing off the article expressing the case for reverting Article IX. Team is reviewing now.
2656
2657Craig Murray - EOS BlockSmith
2658all the eos-bios launches stage 1 to 20 ran that way as well 300-400 lib behind head
2659
2660Zhao Yu@ EOSLaoMao.com
2661Just want to mention that the new chain will honor unregistered users right?
2662
2663Jae Chung - HKEOS
2664mini - EOS Argentina
2665Yes shouldn't be 325, don't know if has anything to do with the boot process.
2666The LIB updates in logs every time you go to the next  producer, it looks something like this:
2667ncy: 3989 ms]
26681385989ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 910ac250b05781d0... #319206 @ 2018-06-07T17:23:02.000 signed by ccccccccccc1 [trxs: 0, lib: 318877, conf: 0, latency: 3989 ms]
26691386492ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 9e4af3985fc8b100... #319207 @ 2018-06-07T17:23:02.500 signed by ccccccccccc1 [trxs: 0, lib: 318877, conf: 0, latency: 3992 ms]
26701386988ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block dacc179065da6452... #319208 @ 2018-06-07T17:23:03.000 signed by ccccccccccc1 [trxs: 0, lib: 318877, conf: 0, latency: 3988 ms]
26711387488ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 4423d0ae362579e6... #319209 @ 2018-06-07T17:23:03.500 signed by ccccccccccc1 [trxs: 0, lib: 318877, conf: 0, latency: 3988 ms]
26721387989ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 41237899f203295e... #319210 @ 2018-06-07T17:23:04.000 signed by ccccccccccc1 [trxs: 0, lib: 318877, conf: 0, latency: 3989 ms]
26731388488ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 71e0227b5344b4e0... #319211 @ 2018-06-07T17:23:04.500 signed by ccccccccccc1 [trxs: 0, lib: 318877, conf: 0, late
2674ncy: 3989 ms]
26751388989ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 1a8978b3f7a8a272... #319212 @ 2018-06-07T17:23:05.000 signed by ccccccccccc1 [trxs: 0, lib: 318877, conf: 0, latency: 3989 ms]
26761389490ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 859105995a15d10c... #319213 @ 2018-06-07T17:23:05.500 signed by ccccccccccc1 [trxs: 0, lib: 318877, conf: 0, latency: 3990 ms]
26771389989ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 9cfd15544a461c51... #319214 @ 2018-06-07T17:23:06.000 signed by ddddddddddd1 [trxs: 0, lib: 318889, conf: 216, latency: 3989 ms]
26781390488ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 455f1cb2bceed455... #319215 @ 2018-06-07T17:23:06.500 signed by ddddddddddd1 [trxs: 0, lib: 318889, conf: 0, latency: 3988 ms]
26791390988ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block 0dba201cd93c56b1... #319216 @ 2018-06-07T17:23:07.000 signed by ddddddddddd1 [trxs: 0, lib: 318889, conf: 0, latency: 3988 ms]
26801391488ms thread-0   producer_plugin.cpp:290       on_incoming_block    ] Received block ff111dc7f4185cb4... #319217 @ 2018-06-07T17:23:07.500 signed by ddddddddddd1 [trxs: 0, lib: 318889, conf: 0, latency: 3988 ms]
2681I wouldn't be so fast to call it a problem in the boot process or a bug in the software @moonxor ;)
2682
2683Craig Murray - EOS BlockSmith
2684yes lib moves at the end of the producers turn, but still follows behind getting it's 15/21 signatures to be lib
2685
2686mini - EOS Argentina
2687I said I didn't know
2688
2689Marc-Antoine Ross - EOS Canadaadmin
2690Zhao Yu@ EOSLaoMao.com
2691Just want to mention that the new chain will honor unregistered users right?
2692Yes
2693
2694Zhao Yu@ EOSLaoMao.com
2695Got some holders who forget to register asking, so just want to make sure
2696
2697Craig Murray - EOS BlockSmith
2698Zhao Yu@ EOSLaoMao.com
2699Got some holders who forget to register asking, so just want to make sure
2700yes 100%
2701
2702Nate D - Aloha EOS
2703What about unregistered holders that had erc20 EOS in an ETH wallet where that wallet never sent any ETH or EOS? Was the issue of those wallets not being in the snapshot resolved?
2704
2705Craig Murray - EOS BlockSmith
2706Nate D - Aloha EOS
2707What about unregistered holders that had erc20 EOS in an ETH wallet where that wallet never sent any ETH or EOS? Was the issue o
2708i do not believe there is any problem with that.  The addresses are recorded, and a mechanism can be built to retrive them given the user has the private key and can sign an eth tx to prove it.  This is my understanding of the current state
2709
2710Thomas "Disclaimer" Cox (all opinions mine)
2711It is the shared belief of the Arbitration Team and of me, Thomas, that the last-minute change to Article IX be reverted. This community is ready to govern itself. It should face that self governing future with confidence.
2712
2713https://forums.eosgo.io/discussion/1189/the-case-for-reverting-article-ix-9/p1?new=1
2714
2715EOS Go
2716The Case for Reverting Article IX (9)
2717This article explains why Article IX (9) "Dispute Resolution" should have the changes of 30-May-2018 reverted. Situation
2718This is the write-up I promised on the 0100 call
2719Ben Sigman invited Kartik Mandaville | SpringRole
2720
2721Ben Sigman
2722Kevin Rose - EOS New York
2723Put what you want into the criteria list. The best way to solicit consensus is when that list is final and pushed back out to th
2724Where is this list?
2725
2726Josh Kauffman - EOS Canada
2727If you check the notes from today's call, there should be links in there
2728@Bensig https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c
2729
2730Google Docs
2731GoNoGo Call
2732Wednesday 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, E...
2733
2734Ben Sigman
2735Josh Kauffman - EOS Canada
2736If you check the notes from today's call, there should be links in there
2737Thank you
2738Josh Kauffman - EOS Canada
2739If you check the notes from today's call, there should be links in there
2740Actually, I do not see any links in there for documents.
2741
2742Josh Kauffman - EOS Canada
2743Shoot that's my bad, I grabbed the one from yesterday's call. One sec, gonna get the right link.
2744https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=753803902
2745
2746Google Docs
2747EOS Mainnet Validation Plan
2748Validation Tools
2749
2750Name, Scope of Tests, BPs who will execute, How Long for Execution?
2751Firestarter from EOS Argentina, Injects csv, tool agnostic, sy...
2752that's the one that has the ABP criteria
2753
2754Roshan - EOS Authority
2755Daniel LarimerJun 7, 2018 2:46:12 PM
2756Just a reminder we will be releasing 1.0.2 tomorrow with enhancements / bug fixes for the whitelist / blacklist feature.   We will be doing weakly updates to fix rough edges, but nothing hard forking.
2757
2758Sharif Bouktila - EOS Dublinadmin
2759For what it’s worth from everything we’ve seen so far with ECAF, we fully support the latest change and are confident ECAF will be able to handle any and all cases needed from launch. 
2760
2761One thing they will need is a close relationship and open lines of communication with our BPs , there will be a lot of manual processes involved for quite a while.
2762
2763Timothy Lewis
2764Sharif Bouktila - EOS Dublin
2765Ok - We have a process , I suggest we put it on the agenda at 01:00 UTC @jemxpat @michaelyeates @trustlayer @abourget @marcant
2766Excited.
2767
2768Jae Chung - HKEOS
2769https://github.com/EOSIO/eos/issues/3917
2770GitHub
2771Assertion exception on get accounts #3917
2772OS: Ubuntu 18.04 (cleos.sh is a script that runs cleos -u &lt;http-server-address&gt;) As shown below, get account throws an assert exception on some...
2773https://github.com/EOSIO/eos/issues/3918
2774GitHub
2775Transfer action does not work at times #3918
2776LIB was moving with head block quite closely (within 400), and the transfer action was pushed multiple times. However, none of these transfers seem to...
2777found some things while testing in the last couple of hours which we've filed
2778seems like they should be addressed soon, #3918 could be critical
2779
2780Denis | EOS Nation
2781Jae Chung - HKEOS
2782found some things while testing in the last couple of hours which we've filed
2783:+1:Thanks for sharing Jae, great finds, at least using the -j flag can workaround this issue (for now until resolved)
2784
2785Jae Chung - HKEOS
2786Denis | EOS Nation
2787:+1:Thanks for sharing Jae, great finds, at least using the -j flag can workaround this issue (for now until resolved)
2788yep, and I think Dan will solve #3917 with tomorrow's 1.0.2 release
2789
2790Kyle - EOSVibes
2791Thomas "Disclaimer" Cox (all opinions mine)
2792It is the shared belief of the Arbitration Team and of me, Thomas, that the last-minute change to Article IX be reverted. This c
2793Boom!:boom: Good on yea Tom cat! :white_check_mark:
2794I’m very happy to see this (apologies for the over-enthusiastic response) :blush:
2795
2796Jae Chung - HKEOS
2797but #3918 needs attention, it could be quite dangerous
2798
2799Denis | EOS Nation
2800Jae Chung - HKEOS
2801but #3918 needs attention, it could be quite dangerous
2802🤔I agree with Dan's comment, not too sure if that's a bug in cleos or network forks/local node environment.
2803
2804Dan tagged it as "support" (might not be a bug)
2805
2806Alexandre Bourget - EOS Canada
2807Yeah I remember experiencing that when some nodes were not fully sync'd ...
2808it's quite surprising, though !
2809We also found that, depending on network topology, setting p2p-max-nodes-per-host helps..
2810we were often trying to connect many times to a node from the same office IP.. so some wouldn't be sync'd..
2811but it wasn't immediately obvious
2812Jason Wang - EOS Pacific joined group via invite link
2813Dr Ye EOS WashingtonDC - TChain joined group via invite link
2814Dr Ye EOS WashingtonDC - TChain
2815kicking .. just prevent from being kicked out again :-)
2816Is 597a still the only mainnet candidate as we voted two days ago? sorry missed the latest status
2817
2818Marc-Antoine Ross - EOS Canadaadmin
2819Dr Ye EOS WashingtonDC - TChain
2820Is 597a still the only mainnet candidate as we voted two days ago? sorry missed the latest status
2821No, there will be a new chain launched by the anonymous ABP
2822Dr Ye EOS WashingtonDC - TChain
2823ok. just let us know the new genesis and peer list
2824Jason Wang - EOS Pacific
2825Marc-Antoine Ross - EOS Canada
2826No, there will be a new chain launched by the anonymous ABP
2827do you knwo if we have anonymous ABP selected already?
2828
2829Timothy Lewis
2830Jason Wang - EOS Pacific
2831do you knwo if we have anonymous ABP selected already?
2832Not yet
2833
2834David P - EOS42
2835Timothy Lewis
2836Not yet
2837Can ask Kevin Rose shortly he’ll be arriving at Tulip in about half an hour
2838But yes not yet we’ll get an update on the call in 3hrs
2839
2840Douglas Horn | EOSAmericas
2841For the upcoming call, we are bringing in our Korean-speaking team member to translate summaries in Korean during the call (in the Chat section). He can also translate any questions back into English. We want to test this out and if it works well, we will add more languages in the next few calls. Hopefully Chinese first. We think it will help the call go more efficiently. This morning there were some times when the discussion went on for a while without translation. Also, the current system puts a lot of responsibility on EOS Asia.
2842Please let us know if you think it's a model worth exploring and we will try to get more of our multilingual team deployed on future calls.
2843Dr Ye EOS WashingtonDC - TChain
2844zoom link for the call?
2845
2846Marc-Antoine Ross - EOS Canadaadmin
2847All,
2848
2849For internal use only for the EOS Validation (EMLG) Telegram Channel. Please do not share outside of this channel.
2850
2851Here's the proposed agenda:
2852
2853Re-ratify on next call the 2/3+1 for Go/NoGo
2854Constitution change vote + update on changes
2855ABP selection update
2856No P0 P1 reported?
2857Voting Portal update
2858Go/NoGO vote
285948 hour update + coordination of the announcements
2860
2861https://zoom.us/j/326472166
2862
2863Zoom Video
2864Join our Cloud HD Video Meeting now
2865Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
2866Marc-Antoine Ross - EOS Canada pinned « All, For internal use only for the EOS Validation (EMLG) Telegram Channel. Please do not share outside of this channel. Here's»
2867
2868deck - EOS New York
2869Douglas Horn | EOSAmericas
2870Please let us know if you think it's a model worth exploring and we will try to get more of our multilingual team deployed on fu
2871Hey Doug, we usually use the chat window for votes so it is hard to get messages to stay on screen but I say give it a go
2872
2873Rick Schlesinger - EOS New York
2874please dont forward the zoom link
2875
2876Douglas Horn | EOSAmericas
2877deck - EOS New York
2878Hey Doug, we usually use the chat window for votes so it is hard to get messages to stay on screen but I say give it a go
2879Yes, I've been on the last several calls. We've been working up ideas for helping out the process where possible. I've asked him to just do summaries. I'm thinking Korean and Chinese might be enough.
2880Rick Schlesinger - EOS New York
2881please dont forward the zoom link
2882We're not forwarding it. It's to our team member.
2883
2884Rohan - EOSauthority
2885Rick Schlesinger - EOS New York
2886please dont forward the zoom link
2887Ok
2888
2889Rick Schlesinger - EOS New York
2890im saying dont forward it to public channels. you can provide to your team members of course.
2891
2892Rohan - EOSauthority
2893Is the link out yet?
2894
2895Douglas Horn | EOSAmericas
2896:+1:
2897
2898Rohan - EOSauthority
2899Can’t find it anywhere?
2900
2901Rick Schlesinger - EOS New York
2902scroll up about 7 lines
2903
2904Rohan - EOSauthority
2905Rick Schlesinger - EOS New York
2906scroll up about 7 lines
2907I think it’s my 2AM brain. Thanks.
2908
2909Alexandre Bourget - EOS Canada
2910@daniellarimer hey Dan, what would be the impact of transfering all EOS out the eosio.ram and eosio.ramfee accounts, before eosio resignation ?
2911
2912Daniel Larimer
2913Ram is used by market maker
2914Ramfee is at community disposal
2915
2916Roman CryptoLions
2917@jemxpat
2918
2919jem
2920Alexandre Bourget - EOS Canada
2921@daniellarimer hey Dan, what would be the impact of transfering all EOS out the eosio.ram and eosio.ramfee accounts, before eosi
2922No user "gifted" with ram would be able to sell until some other user buys new ram post 15% activation. Tested.
2923
2924Daniel Larimer
2925jem
2926No user "gifted" with ram would be able to sell until some other user buys new ram post 15% activation. Tested.
2927It violates bancor algorithm invariant
2928
2929Kyunghwan Kim - EOSeoul.io
2930transfer of token doesn’t impact price of ram. price of ram is determined in bancor state in rammarket db only through buy/sellram for now.
2931
2932and transfer of token doesn’t impact the supply of token, also.
2933
2934jem
2935KHKim is correct. There is no violation of Bancor with this method.
2936
2937Daniel Larimer
2938Kyunghwan Kim - EOSeoul.io
2939transfer of token doesn’t impact price of ram. price of ram is determined in bancor state in rammarket db only through buy/sellr
2940It prevents market maker from filling orders
2941
2942jem
2943Only until new user buys ram.
2944
2945David Moss
2946Dan, we need a comment on https://github.com/EOSIO/eos/issues/3918
2947GitHub
2948Transfer action does not work at times #3918
2949LIB was moving with head block quite closely (within 400), and the transfer action was pushed multiple times. However, none of these transfers seem to...
2950Marshall - SaltBlock invited Robrigo - EOS Detroit
2951
2952Robrigo - EOS Detroit
2953Thanks for the add @marshallslc.
2954
2955Marshall - SaltBlock
2956You're welcome
2957
2958Andrey Marchuk
2959Tulip conf cannot join back because of 200 participants limits
2960
2961Thomas "Disclaimer" Cox (all opinions mine)
2962TRY AGAIN in a few minutes
2963
2964Ben Sigman
2965https://docs.google.com/spreadsheets/d/1gJnn0KS4rgDnTowPlN80gulVI77lRgldPhH17kZOnnI/edit#gid=744644035
2966
2967Google Docs
2968EOS Voting Portal Audit
2969About
2970
2971This spreadsheet is a list compiled by members of the EOS community( EMLG)
2972It is a list of all known EOS voting portals
2973This list is compile...
2974
2975Alexandre Bourget - EOS Canada
2976@daniellarimer do you think it makes sense to create an eosio.burned account, where we can put things in ?
2977If you're planning a recall action, maybe it's useless..
2978
2979Chitty 🅑 - EOS Argentina
2980Is phill from eos switzerland here?.. I am just wondering if they are a bp since I havent seen them before
2981
2982Jose Toriello
2983Chitty 🅑 - EOS Argentina
2984Is phill from eos switzerland here?.. I am just wondering if they are a bp since I havent seen them before
2985Good question
2986Heejae - EOSYS.io
2987Chitty 🅑 - EOS Argentina
2988Is phill from eos switzerland here?.. I am just wondering if they are a bp since I havent seen them before
2989Me too.
2990
2991Chitty 🅑 - EOS Argentina
2992I think there are a couple of fake bps in the chat
2993
2994Igor Lins e Silva - EOS Rio
2995Chitty 🅑 - EOS Argentina
2996I think there are a couple of fake bps in the chat
2997:+1:
2998
2999Rick Schlesinger - EOS New York
3000do the vote here?
3001
3002J.T. - EOS the World
3003Yes.
3004Or post a new straw poll here.
3005An Byung Chan - EOSYS invited Lievin Kim - EOSYS
3006
3007David P - EOS42
3008I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3009Ricardo Marlière - EOS Brazil invited EOS - Antarctica
3010
3011Ross (EOSphere)
3012Was thinking the same
3013
3014mini - EOS Argentina
3015David P - EOS42
3016I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3017Me neither
3018
3019Chitty 🅑 - EOS Argentina
3020he is fake, and looks like a troll
3021
3022J.T. - EOS the World
3023agreed.
3024Pascal Van Wy | EOS Network by Advanced Blockchain AG
3025agreed
3026
3027Patrick B - Aloha EOS
3028He's definitely trolling
3029
3030Rohan - EOSauthority
3031David P - EOS42
3032I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3033Good find..
3034
3035Rick Schlesinger - EOS New York
3036David P - EOS42
3037I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3038+1
3039
3040Alex - EOS SOCAL
3041David P - EOS42
3042I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3043+1
3044
3045Hubert Chang-EOSeoul.io
3046Can we kick him out from the call?
3047
3048Jacky - JEDA
3049David P - EOS42
3050I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3051+1
3052David P - EOS42
3053I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3054+1
3055David P - EOS42
3056I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3057+1
3058
3059David P - EOS42
3060Yes please
3061And various others who are clear no’s
3062
3063Khosi Morafo eosAfrica
3064David P - EOS42
3065I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3066+1
3067
3068Denis | EOS Nation
3069+1 for ELMG voting
3070
3071Andrey Marchuk
3072+1
3073
3074Kevin Rose - EOS New York
3075David P - EOS42
3076I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3077+1
3078
3079Craig Murray - EOS BlockSmith
3080+1
3081Ben Sigman invited Kurt Braget | White Rabbit ICOs
3082Bean@EOS Cannon
3083+1
3084Pascal Van Wy | EOS Network by Advanced Blockchain AG
3085+1
3086jem invited Nick eos.fish
3087
3088Cryptosufi - 威杰 - BitSpace
3089David P - EOS42
3090I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3091+1
3092
3093Eric - sw/edenadmin
3094Can we postpone the vote until 13:00 and have some tool ready?
3095Nick eos.fish
3096Thank you Jem!
3097
3098Denis | EOS Nation
3099Eric - sw/eden
3100Can we postpone the vote until 13:00 and have some tool ready?
3101:-1:
3102
3103Issay@OracleChain
3104Nick eos.fish
3105Thank you Jem!
3106+1
3107
3108Douglas Horn | EOSAmericas
3109Eric - sw/eden
3110Can we postpone the vote until 13:00 and have some tool ready?
3111:-1:
3112Nick eos.fish
3113David P - EOS42
3114I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
3115+1
3116
3117Chitty 🅑 - EOS Argentina
3118Eric - sw/eden
3119Can we postpone the vote until 13:00 and have some tool ready?
3120we have most bps online now, lets vote
3121
3122Cryptosufi - 威杰 - BitSpace
3123Eric - sw/eden
3124Can we postpone the vote until 13:00 and have some tool ready?
3125We could start cleos voting, until audited tools arrive.
3126
3127Eric - sw/edenadmin
3128I'm up for whatever, this just feels like a farce...
3129
3130Rohan - EOSauthority
3131Please stop posting messages.. wait for Sharif’s question and then vote..
3132
3133Josh Kauffman - EOS Canada
3134-----------------------------------------------------------------------------------------------------------------------------
3135PLEASE DO NOT WRITE ANYTHING BELOW THIS UNTIL THOMAS HAS POSTED THE QUESTION IN THIS CHANNEL
3136-----------------------------------------------------------------------------------------------------------------------------
3137
3138Thomas "Disclaimer" Cox (all opinions mine)
3139[Sharif will post the question]
3140You need permission
3141This form can only be viewed by users in the owner's organization.
3142
3143Sharif Bouktila - EOS Dublinadmin
3144Please confirm using GO/ NO GO to launch at 13:00 UTC 8th June 2018 using current release.
3145
3146Denis | EOS Nation
3147No need for form
3148
3149Cryptosufi - 威杰 - BitSpace
3150Go
3151
3152Sebastian Castro - EOS Argentina 🇦🇷
3153Go
3154
3155Ralf Weinand | GenerEOS (BP Sydney)
3156Go
3157
3158James Sutherland - Cypherglass.com
3159Go
3160
3161Rohan - EOSauthority
3162Sharif Bouktila - EOS Dublin
3163Please confirm using GO/ NO GO to launch at 13:00 UTC 8th June 2018 using current release.
3164Go - EOS Authority
3165
3166Alex - EOS SOCAL
3167Go
3168
3169Nate D - Aloha EOS
3170GO
3171
3172Marek EOSEmerge.io - Poland
3173GO
3174
3175Domi - EOS Rio
3176the abp wasn't even selected, poor him if it's a go
3177
3178EOS - Antarctica
3179No go.
3180
3181zhangzc | Onechain
3182GO
3183
3184Jose Toriello
3185Go
3186
3187Craig Murray - EOS BlockSmith
3188go
3189
3190Andrey Marchuk
3191Go - BlockEOS.io
3192
3193Jorge Ferrando - EOSMetal
3194Go
3195
3196Denis | EOS Nation
3197GO
3198
3199Ross (EOSphere)
3200Go
3201
3202crazybit@SuperONE.io
3203Go Go Go
3204
3205Marshall - SaltBlock
3206Go
3207
3208deck - EOS New York
3209go
3210
3211Kedar Iyer | LibertyBlock
3212GO
3213Nick eos.fish
3214Go
3215
3216Joshua Qiu @EOSeco
3217Go
3218Robert DeWilder - Worbli
3219go
3220
3221Miłosz Eos Emerge - Poland
3222Go
3223
3224Sharif Bouktila - EOS Dublinadmin
3225No Go
3226
3227Eric - sw/edenadmin
3228No Go
3229Jason Wang - EOS Pacific
3230Go
3231
3232Jialin Li - EOS WTZ
3233Go
3234
3235jem
3236jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet
3237No Go
3238
3239Hugo Yang - EOS Silicon Valley
3240No go
3241
3242Timothy Lewis
3243No go
3244
3245Issay@OracleChain
3246NO GO
3247
3248Igor Lins e Silva - EOS Rio
3249No go
3250
3251Basit Raza - EOSVibes
3252GO
3253
3254Marc-Antoine Ross - EOS Canadaadmin
3255Go
3256
3257ndoy |EOS Cafe: Calgary |
3258GO
3259
3260Ian(Yahuang Wu) - MEET.ONE
3261NO GO.
3262
3263Pete BlockMatrix
3264no go
3265
3266Zhao Yu@ EOSLaoMao.com
3267GO
3268
3269Ricardo Marlière - EOS Brazil
3270no go... why the rush? 1.0.2 is not even out
3271
3272Jacky - JEDA
3273GO
3274
3275Celu - Blockgenic
3276Go
3277
3278zhangzc | Onechain
3279GO
3280
3281J.T. - EOS the World
3282No Go.
3283
3284Ravi (Blockpro.one)
3285No Go
3286
3287Gordo | HelloEOS
3288go
3289Deadlock@eosio.sg
3290no go
3291
3292Robin Wen@SuperONE.io
3293Go
3294
3295Dafeng Guo - EOS Asia
3296Go
3297
3298WinLin-EOSBIXIN
3299GO
3300
3301Ben Sigman
3302No Go
3303
3304David P - EOS42
3305No go
3306
3307Emily Bush - shEOS
3308No go
3309Pascal Van Wy | EOS Network by Advanced Blockchain AG
3310No Go
3311Heejae - EOSYS.io
3312GO
3313
3314Guillaume @eostitan.com
3315No go
3316
3317heipacker eosunion
3318go
3319
3320Hubert Chang-EOSeoul.io
3321No go
3322
3323Bohdan CryptoLions 🦁
3324no go
3325
3326Luis Fernando G : EOSMESOdotio 🇬🇹
3327No go
3328
3329Yvonne (EOShenzhen)
3330no go
3331
3332Zhao Yu@ EOSLaoMao.com
3333Yvonne (EOShenzhen)
3334no go
3335duplicate
3336
3337Robrigo - EOS Detroit
3338no go
3339
3340Douglas Horn | EOSAmericas
3341No go
3342phajek eosarmy Patrick
3343no go
3344Robrigo - EOS Detroit invited jesta — Greymass
3345jesta — Greymass
3346go
3347
3348Thomas "Disclaimer" Cox (all opinions mine)
3349END OF VOTING END OF VOTING END OF VOTING
3350
3351Jose Toriello
3352(Eosmeso 1 vote is no go. Sorry for confusion)
3353
3354Mathieu Boulianne - EOS Canada
3355On another note, on the Print / Work Out vote, I got (after cleaning the data): 
3356-55 Print
3357-31 work out
3358
3359jem
3360Appoint ABP, let hiim get ready.
3361
3362Denis | EOS Nation
3363I believe the "no go" is about the RAM disagreement
3364
3365Timothy Lewis
3366There is a lot of deleting going on in this channel
3367
3368Jose Toriello
3369Jose Toriello
3370(Eosmeso 1 vote is no go. Sorry for confusion)
3371Reason was no clarity on print/ram issue
3372
3373Craig Murray - EOS BlockSmith
3374Jose Toriello
3375Reason was no clarity on print/ram issue
3376dan was very clear we should not take the RAM balance
3377Dan said there is only 1 good option, print
3378
3379Sharif Bouktila - EOS Dublinadmin
3380I've deleted some comments in the voting window
3381
3382Sebastian Castro - EOS Argentina 🇦🇷
3383Craig Murray - EOS BlockSmith
3384Dan said there is only 1 good option, print
3385+1
3386
3387Sharif Bouktila - EOS Dublinadmin
3388Only Me , Marc and Eric are admins
3389
3390Robrigo - EOS Detroit
3391My specific reason is waiting to launch with v1.0.2 tag. Would vote GO after tomorrow.
3392
3393Timothy Lewis
3394Robrigo - EOS Detroit
3395My specific reason is waiting to launch with v1.0.2 tag. Would vote GO after tomorrow.
3396Same
3397
3398Jose Toriello
3399Craig Murray - EOS BlockSmith
3400Dan said there is only 1 good option, print
3401I know. But the vote was not counted
3402
3403Craig Murray - EOS BlockSmith
3404why not wait to 1.0.3? or 1.1? or 2.0?
3405no major issues fixed in 1.0.2
3406
3407Robrigo - EOS Detroit
3408Because 1.0.3 is 8 days away, not 1 day away
3409jesta — Greymass
3410You wouldn't even have to upgrade to 1.0.2 immediately.
3411
3412Robrigo - EOS Detroit
3413You asked, I answered :)
3414
3415Timothy Lewis
3416We also will likely get an opinion from Dan on the lost transaction issue.
3417
3418Sherman EOSREAL
3419go
3420
3421Timothy Lewis
3422Get ABP selected
3423
3424Issay@OracleChain
3425Timothy Lewis
3426Same
3427we thought the 3918 issue might be P1, so wait for 1.0.2
3428
3429Timothy Lewis
3430Have them prepare
3431
3432EOS - Antarctica
3433The reasoning for someone’s vote is irrelevant.  We took a vote.  Use the numbers.
3434
3435Thomas "Disclaimer" Cox (all opinions mine)
3436I'm counting 39 GO to 25 NO GO in the telegram channel
3437I can't promise that the data is completely clean
3438
3439Ravi (Blockpro.one)
3440Many BP missing here because not everyone here
3441
3442EOS - Antarctica
3443One does not get to the chance to try and sway opinion after the election.
3444Ben Sigman invited Tal Muskal | LiquidEOS
3445
3446Denis | EOS Nation
3447:-1: 1.0.2 is not a show stopper
3448
3449Jose Toriello
3450Denis | EOS Nation
3451:-1: 1.0.2 is not a show stopper
3452+1
3453
3454Issay@OracleChain
3455but another reason is not all BPs is present here
3456
3457Alexandre Bourget - EOS Canada
3458https://abourget.keybase.pub/votetallysum.txt
3459
3460Jacky - JEDA
3461is 1.0.2 fixes any P0 or P1 issue?
3462
3463Alexandre Bourget - EOS Canada
3464That's my data ^^
3465
3466Nate D - Aloha EOS
3467Jacky - JEDA
3468is 1.0.2 fixes any P0 or P1 issue?
3469No
3470
3471Domi - EOS Rio
3472I'm just concerned with the APB, it wasn't even selected yet, we don't  know what his timezone will be, let him prepare
3473
3474Craig Murray - EOS BlockSmith
3475Jacky - JEDA
3476is 1.0.2 fixes any P0 or P1 issue?
3477no
3478
3479James Sutherland - Cypherglass.com
3480Alexandre Bourget - EOS Canada
3481That's my data ^^
3482:+1:
3483
3484Thomas "Disclaimer" Cox (all opinions mine)
3485The first vote was 52 to 21 //  a 71% YES
3486
3487heipacker eosunion
3488heipacker eosunion
3489go
3490go
3491
3492Jacky - JEDA
3493Craig Murray - EOS BlockSmith
3494no
3495then there is no reason we have to wait for 1.0.2 for my understanding.
3496
3497EOS - Antarctica
3498Why are we taking a vote, if we're not going to put the results into place?
3499
3500Alex - EOS SOCAL
3501Domi - EOS Rio
3502I'm just concerned with the APB, it wasn't even selected yet, we don't know what his timezone will be, let him prepare
3503Agree with this. Should've been sorted earlier than this call. If we wind up with No Go, the APB needs to announce endpoints asap fo syncing.
3504But also regarding that, the schedule was announced long ago. The abp knew this 12 hour slot was a potential go time.
3505Regardless of timezone
3506
3507Issay@OracleChain
3508[Photo]
3509Thomas "Disclaimer" Cox (all opinions mine) invited EOS Malaysia
3510Klob
3511Thanks
3512
3513ndoy |EOS Cafe: Calgary |
3514
3515Issay@OracleChain
3516Photo
3517this might be fake:
3518From deadlock - EOSIO.SG to Everyone:  09:44 PM
3519why celeb has EOSIO.SG website under the name
3520deadlock doesn't know him
3521Klob
3522Sorry, there's been some confusion
3523One second
3524
3525Denis | EOS Nation
3526No go's should provide reasons (not blank no go's)
3527
3528EOS - Antarctica
3529Why? A vote is a vote
3530Lee - EOSTEA
3531go
3532
3533Jose Toriello
3534Some no gos were due to uncertainty on the vote count about RAM. If that is cleared and whichever option has been taken, so the ABP doesnt have to guess. 
3535
3536Then we are changing from no go to GO
3537An Byung Chan - EOSYS invited Ashley Gan
3538
3539Denis | EOS Nation
3540Can't update to 1.0.2, code is not released (maybe released)
3541
3542Marek EOSEmerge.io - Poland
3543too bad that it didn't happen today
3544Its a real pitty that they can't make a good reason for no go
3545
3546zhangzc | Onechain
3547+1
3548
3549Denis | EOS Nation
3550How many hours for validation + meshes (12 hours?)
3551
3552jem
3553Marek EOSEmerge.io - Poland
3554Its a real pitty that they can't make a good reason for no go
3555Yes, when you don't like the vote, be sure to challenge the motivation and reason of the opposition. What a great strategy!