wD7V4EU5

1
2Igor Lins e Silva - EOS Rio
3all data is on chain
4
5Jae Chung - HKEOS
6Loading
7it hasn't been published yet, @igorls will do so now
8
9Marc-Antoine Ross - EOS Canadaadmin
10Jae Chung - HKEOS
11it hasn't been published yet, @igorls will do so now
12:+1:
13
14Craig Murray - EOS BlockSmith
15Jae Chung - HKEOS
16it hasn't been published yet, @igorls will do so now
17thx! :+1:
18
19Marc-Antoine Ross - EOS Canadaadmin
20That will surely help reach full consensus on the content we want on chain, 1 more :heavy_check_mark:!
21
22Jae Chung - HKEOS
23Along with the injector script too.
24
25Igor Lins e Silva - EOS Rio
26
27run_cmd "set contract eosio "$CONTRACTS/eosio.bios" -p eosio";
28run_cmd "create account eosio b1 EOS5cujNHGMYZZ2tgByyNEUaoPLFhZVmGXbZc9BLJeQkKZFqGYEiQ";
29run_cmd "create account eosio eosio.msig $EOSIO_PUB"
30run_cmd "create account eosio eosio.token $EOSIO_PUB"
31run_cmd "create account eosio eosio.ram $EOSIO_PUB"
32run_cmd "create account eosio eosio.ramfee $EOSIO_PUB"
33run_cmd "create account eosio eosio.names $EOSIO_PUB"
34run_cmd "create account eosio eosio.stake $EOSIO_PUB"
35run_cmd "create account eosio eosio.saving $EOSIO_PUB"
36run_cmd "create account eosio eosio.bpay $EOSIO_PUB"
37run_cmd "create account eosio eosio.vpay $EOSIO_PUB"
38run_cmd "push action eosio setpriv "'["eosio.msig",1]'" -p eosio"
39run_cmd "set contract eosio.msig "$CONTRACTS/eosio.msig" -p eosio.msig"
40run_cmd "set contract eosio.token "$CONTRACTS/eosio.token" -p eosio.token"
41cleos push action eosio.token create '["eosio","10000000000.0000 EOS"]' -p eosio.token
42cleos get currency stats eosio.token EOS
43cleos push action eosio.token issue '["eosio",  "1000000000.0000 EOS", "initial issuance"]' -p eosio
44cleos get currency stats eosio.token EOS
45run_cmd "set contract eosio "$CONTRACTS/eosio.system" -p eosio"
46cleos push action eosio buyrambytes '["eosio","b1",8192]' -p eosio
47cleos transfer eosio b1 "10.0000 EOS" "eosacknowledgments.io" -p eosio
48cleos system delegatebw --transfer eosio b1 "49999995.0050 EOS" "49999995.0050 EOS"
49## inject tokens
50## revert eosio to system
51## resign eosio
52here is some boot sequence
53
54jem
55For GB core paused net:
56
57$ cleos get currency stats eosio.token "EOS"
58{
59  "EOS": {
60    "supply": "1000000000.0000 EOS",
61    "max_supply": "10000000000.0000 EOS",
62    "issuer": "eosio"
63  }
64}
65
66Marc-Antoine Ross - EOS Canadaadmin
67Igor Lins e Silva - EOS Rio
68run_cmd "set contract eosio "$CONTRACTS/eosio.bios" -p eosio"; run_cmd "create account eosio b1 EOS5cujNHGMYZZ2tgByyNEUaoPLFhZV
69can this be on github please?
70
71Michael Yeates
72we are very busy validating the software at the moment
73
74Marc-Antoine Ross - EOS Canadaadmin
75we'd like to help @michaelyeates. sharing code helps paralelize work
76
77Igor Lins e Silva - EOS Rio
78Marc-Antoine Ross - EOS Canada
79can this be on github please?
80this draft? is totally irrelevant for validation
81
82Zhao Yu@ EOSLaoMao.com
83jem
84For GB core paused net: $ cleos get currency stats eosio.token "EOS" { "EOS": { "supply": "1000000000.0000 EOS", "max
85how did you manage to do this?
86
87jem
88Loading
89As mentioned before, the fundamental cause of the difference in hash value is the inclusion of the absolute path of the build directory as part of the hashed data. Many have been using "/home/eos" as the base directory from which the code is built, including the boost libraries.
90
91I guess that the base directory used in the Docker build is something different. Perhaps if /home/eos was used, it would give the same hash as we see.
92
93While the hash and data in the files should be independent of the source code location, currently it is not. This is a bug, but overall just an annoyance when understood.
94
95Syed Jafri | EOS Cafe / Calgary
96Loading
97Change path or have these changes: https://github.com/EOSIO/eos/pull/3834/files
98
99Rohan - EOSauthority
100[Photo]
101
102Craig Murray - EOS BlockSmith
103Igor Lins e Silva - EOS Rio
104run_cmd "set contract eosio "$CONTRACTS/eosio.bios" -p eosio"; run_cmd "create account eosio b1 EOS5cujNHGMYZZ2tgByyNEUaoPLFhZV
105should this be in github?
106Branden Espinoza joined group via invite link
107
108Ricardo Marlière - EOS Brazil
109Loading
110:pray:
111
112Thomas "Disclaimer" Cox (all opinions mine)
113What time and link for the next meeting please?
114Report from the Test Protocol Workgroup:
115
116Thomas "Disclaimer" Cox (all opinions mine)
117Thomas "Disclaimer" Cox (all opinions mine)Jun 5, 2018 12:46:37 PM
118Test Protocol group will be preparing a suggested protocol for two things:
1191. How to propose a UA test
1202. How to sign up for & run a UA test and report results
121Work is being done by Branden Espinoza with assist from Sharif and Ross and at least 1 other
122We have a draft statement of UA Testing Exit Criteria we'll be releasing. 
123Work on the draft is being done by Sharif and several others
124The test protocol will be accompanied by a tool or set of tools to make it easier to keep the data accurate and complete
125
126Thomas "Disclaimer" Cox (all opinions mine)
127Timeline is - in 60 minutes we will get a progress report from @espinbrand and an estimated time to completion
128@sharifbouktila will share the draft Exit Criteria statement in I believe that same timeframe
129
130Joshua Qiu @EOSeco
131do we still have meeting in 18 utc ?
132
133Sharif Bouktila - EOS Dublinadmin
134Proposed Validation Exit Criteria 
135
1361. Completed Test Plan verified by multiple BP teams 
1372. No new proposals of critical tests outstanding
1383. Confirmation from the EMLG that Validation is Complete (Go/No Go)
1394. Decision on which chain to enable for staking
140Joshua Qiu @EOSeco
141do we still have meeting in 18 utc ?
142Yes in 6 minutes
143https://zoom.us/j/911102470
144
145Zoom Video
146Join our Cloud HD Video Meeting now
147Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
148
149mini - EOS Argentina
150Zhao Yu@ EOSLaoMao.com
151I do think the proposal that we use bios-boot to inject all the actions, then hand it over to GB to run an ABP node producing bl
152Love this idea
153Igor Lins e Silva - EOS Rio
154validation tools should not follow sequences, they should be able to validade state
155+1
156
157Joshua Qiu @EOSeco
158agree on issue
159
160Sharif Bouktila - EOS Dublinadmin
161Issue more tokens for accounts
162
163Jae Chung - HKEOS
164Option 1: Take From Unregistered Accounts, Return them later on fallback registration
165Option 2: Issue more tokens
166
167Thomas "Disclaimer" Cox (all opinions mine)
168Option 3: Borrow from 'unregistered' balance, pay back loan from producer pay over first N days
169What's the total number of tokens required, roughly?
170
171James Sutherland - Cypherglass.com
172Please say the amount
173
174Nate D - Aloha EOS
175Yes, what is the amount? @abourget
176
177Michael Yeates
178Nate D - Aloha EOS
179Yes, what is the amount? @abourget
18011821
181
182Domi - EOS Rio
183Option 1: Take From Unregistered Accounts, Return them later:
184
185$ cleos get currency stats eosio.token "EOS"
186{
187"EOS": {
188"supply": "1000000000.0000 EOS",
189"max_supply": "10000000000.0000 EOS",
190"issuer": "eosio"
191}
192}
193
194Option 2: Issue more tokens:
195 {
196"EOS": {
197"supply": "1000011821.0000 EOS",
198"max_supply": "10000000000.0000 EOS",
199"issuer": "eosio"
200}
201}
202
203Josh Kauffman - EOS Canada
204WinLin-EOSBIXINJun 3, 2018 5:52:39 AM
205and I run with issued '1,000,011,818.7401 EOS' but failed with error in record_unregsited:
206assertion failure with message: overdrawn balance
207
208so I change issue amount into "1000012000.0000 EOS" and run again, and successed, eosio balnace is 181.0276 EOS, so the final EOS issue should be :
2091000012000.0000 - 181.0276 = 1,000,011,818.9724
210and the eosio.ram and eosio.ramfee may change 1-2 EOS, 
211
212so we can issue once and use 1,000,011,820.0000 EOS, and after BIOS, the balance of eosio is just 1-2 EOS left, which I think is ok
213
214Josh Kauffman - EOS Canada
215so if we round up and call that 12,000 extra tokens. that affects the supply by 0.024% . It also only creates 600 tokens per year extra in inflation. Or only 120 tokens FOR THE WHOLE YEAR that goes towards BP pay.
216
217Sharif Bouktila - EOS Dublinadmin
218We can adjust inflation later to reduce supply , or repay from a Worker Proposal
219
220Ravi (Blockpro.one)
221Are you guys only validating the snapshot or also if things like regProducer works?
222
223James Sutherland - Cypherglass.com
224Both.  Data validation and Software function validation
225
226Ravi (Blockpro.one)
227James Sutherland - Cypherglass.com
228Both. Data validation and Software function validation
229My regProducer call is returning no active private key error.. though wallet is open and private keys are visible there
230Check my messages in bios boot channel
231New account creation worked without a hitch
232But regProducer not working
233Josh Kauffman - EOS Canada invited Ovi - eosromania22 - BP
234
235James Sutherland - Cypherglass.com
236Very busy right now @ravincal but I wil ltry to hook up with you later.
237
238Timothy Lewis
239If your BP is on this list, MSG me:
240
241boot.eostitan.com 
242ec2-18-188-4-97.us-east-2.compute.amazonaws.com
243m.jeda.one
244api.eosuk.io
245node.eosmeso.io
246prod.mainnet.eos.cybex.io
247ec2-18-188-38-75.us-east-2.compute.amazonaws.com
248fullnode.eoslaomao.com 
24935.234.53.243
250 eosboot.chainrift.com
251boot.eostitan.com 
252ec2-54-95-202-14.ap-northeast-1.compute.amazonaws.com
253
254Rohan - EOSauthority
255Timothy Lewis
256If your BP is on this list, MSG me: boot.eostitan.com ec2-18-188-4-97.us-east-2.compute.amazonaws.com m.jeda.one api.eosuk.io
257Is being on the list a good thing or a bad thing? 🙂
258
259Timothy Lewis
260no comment.
261
262Shaheen Counts - EOS BlockSmith
263Haha
264
265Rohan - EOSauthority
266:joy:
267
268Marshall - SaltBlock
269I can stop sweating now
270
271Andrey Marchuk
272🙂
273
274Ravi (Blockpro.one)
275Timothy Lewis
276If your BP is on this list, MSG me: boot.eostitan.com ec2-18-188-4-97.us-east-2.compute.amazonaws.com m.jeda.one api.eosuk.io
277Sent you Dm
278
279Craig Murray - EOS BlockSmith
280Timothy Lewis
281If your BP is on this list, MSG me: boot.eostitan.com ec2-18-188-4-97.us-east-2.compute.amazonaws.com m.jeda.one api.eosuk.io
282woot! my name didnt show up... :sweat_smile:
283Timothy Lewis
284If your BP is on this list, MSG me: boot.eostitan.com ec2-18-188-4-97.us-east-2.compute.amazonaws.com m.jeda.one api.eosuk.io
285also thank you for doing this, very important
286
287Luke Stokes
288As requested on the Zoom call, here are the screenshots I mentioned of the conversation with Dan. His criteria five days ago:
289
2901. Does someone lose money?
291
2922. Is there down time?
293
2943. Does the chain just pause for 24 hours while we fix it?
295
296He goes on to say his primary concern is the loss of private keys since we do not have account recovery for these early accounts generated via the snapshot. If we're not dealing with a category 1 or 2 issue, we should be in a pretty good place to launch. Category 3 would be very unfortunate, but something we can recover from. As Dan said 5 days ago "I don't think the current test network is actually invalid" (which would imply it's valid).
297Luke Stokes
298As requested on the Zoom call, here are the screenshots I mentioned of the conversation with Dan. His criteria five days ago: 1
299[Photo]
300
301James Sutherland - Cypherglass.com
302Luke Stokes
303As requested on the Zoom call, here are the screenshots I mentioned of the conversation with Dan. His criteria five days ago: 1
304+1
305
306Luke Stokes
307
308Luke Stokes
309Photo
310[Photo]
311Now for my personal opinion: if we don't have mission critical bugs, we should move forward. There will be more bugs discovered in the future in production, regardless of how much sanitized testing we do under lab conditions. Continuing to find bugs this late in the process is certainly concerning, but if they aren't show stoppers, we should be able to deal with it. The best penetration testers I've ever seen come from unconvention sources, not from structured security firms. The sooner we get this out there live, the sooner we'll know what we're really dealing with.
312
313mini - EOS Argentina
314+1 to @lukestokes
315
316Marshall - SaltBlock
317Luke Stokes
318Now for my personal opinion: if we don't have mission critical bugs, we should move forward. There will be more bugs discovered
319Agreed. Everyone is anxious to get it launched and tensions are high. I think there may be a misconception that people are searching for bugs blindly, but really are just making sure the software works as intended through the entire process. Once we can be sure everything works as intended I dont think anyone is calling for testing beyond that.
320
321Michael Yeates
322Marshall - SaltBlock
323Agreed. Everyone is anxious to get it launched and tensions are high. I think there may be a misconception that people are searc
324:+1:
325
326deck - EOS New York
327Marshall - SaltBlock
328Agreed. Everyone is anxious to get it launched and tensions are high. I think there may be a misconception that people are searc
329+1
330
331Denis | EOS Nation
332:+1: @lukestokes Thanks for sharing, very valuable information
333
334Joshua Qiu @EOSeco
335
336Luke Stokes
337Photo
338agreed
339
340Luke Stokes
341I've shared the above message in various channels, but feel free to share further if it's helpful. I'm excited to see this thing launch and then enjoy the wild ride we find ourselves on after that. 🙂
342
343Jae Chung - HKEOS
344Luke Stokes
345Now for my personal opinion: if we don't have mission critical bugs, we should move forward. There will be more bugs discovered
346:+1:
347
348Thomas "Disclaimer" Cox (all opinions mine)
349Luke Stokes
350As requested on the Zoom call, here are the screenshots I mentioned of the conversation with Dan. His criteria five days ago: 1
351Excellent thank you
352
353Marc-Antoine Ross - EOS Canadaadmin
354Just to recap my recommendation: 
355 
356A) We continuously improve security of the network (multiple initiatives going on now to help, thanks to @trustlayer @dftle) 
357 
358In parallel: 
3591. We agree on the optimal boot sequence (is RAM buying the only issue to solve?) 
3602. We code it (if not already done) and review open source implementation 
3613. We inject it (if not already done) on a swarm of nodes that includes everyone 
3624. We test it (insert Thomas' test report spreadsheet here) 
3635. We select an ABP to hold custody of the network until the 15% vote is done 
3646. We make sure we are all meshed together and help hide the ABP 
3657. We announce validation and voting starts. 
366 
367Please note: No one can brag about the software used, being the boot node or the ABP. We just don't care!! 
368 
369We are all working together to make this better for the token holders.
370
371mini - EOS Argentina
372Marc-Antoine Ross - EOS Canada
373Just to recap my recommendation: A) We continuously improve security of the network (multiple initiatives going on now to hel
374+1
375
376Luke Stokes
377Marc-Antoine Ross - EOS Canada
378Just to recap my recommendation: A) We continuously improve security of the network (multiple initiatives going on now to hel
379Sounds good to me, though I have had concerns with the "code it" part in the past if it could lead to any possible security concerns. To me, the key step is the validation of the chain. However that chain is created doesn't matter to me as much as it being a valid chain. Once we have a valid chain (regardless of the process), I'm happy to go live with it without caring who created it or how it was created.
380
381Patrick B - Aloha EOS
382Marc-Antoine Ross - EOS Canada
383Just to recap my recommendation: A) We continuously improve security of the network (multiple initiatives going on now to hel
384:+1:
385
386Marc-Antoine Ross - EOS Canadaadmin
387Luke Stokes
388Sounds good to me, though I have had concerns with the "code it" part in the past if it could lead to any possible security conc
389+1
390
391Luke Stokes
392
393Luke Stokes
394Photo
395Related to the concerns here Dan mentioend about web portals for voting, I'd like to make sure people know about this desktop voting tool @jestagram created: https://steemit.com/eos/@greymass/announcing-eos-voter-an-eos-block-producer-voting-tool-and-light-wallet
396
397I've used his Vessel wallet before on STEEM along with many other products he's built over the last (almost) two years. They are soild. I helped him test this on the Jungle Testnet when he first launched it, and it worked well.
398
399I much prefer independent blockchain applications over the old model of centralized points of failure (website servers which can be hacked, DNS which can be hacked, domains which can be phished, etc). To me, moving our community away from "use this website" to "use this open-source, trusted tool" is a better approach long term.
400
401Steemit
402Announcing EOS-Voter, an EOS Block Producer Voting Tool & Light Wallet — Steemit
403With the launch of EOS just around the corner, we wanted to release the current iteration of our EOS light wallet… by greymass
404
405Thomas "Disclaimer" Cox (all opinions mine)
406BPs doing testing, please join the Zoom testing call at the top of the current hour (in 6 minutes)
407https://zoom.us/j/5788946547
408
409Zoom Video
410Join our Cloud HD Video Meeting now
411Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
412Timothy Lewis invited ndoy |EOS Cafe: Calgary |
413
414ndoy |EOS Cafe: Calgary |
415Thanks @trustlayer !
416
417Roman CryptoLions
418Link to document?
419
420ndoy |EOS Cafe: Calgary |
421Brandon is updating
422
423Thomas "Disclaimer" Cox (all opinions mine)
424Summary of testing meeting:
4251. All test DEFINITIONS to be entered within 49 minutes of now
4262. Links to the data entry forms (2) and spreadsheet (1) will be posted here as soon as Branden makes the requested changes
4273. All test RESULTS to be added ASAP, by 2300 UTC preferred.
4284. If you have a bunch of results in a file, you can paste a link to the file in the 'results' field -- you don't have to laboriously re-enter old data
429
430Rohan - EOSauthority
431Thanks Branden for putting together the document so quickly
432
433Jose Toriello
434Rohan - EOSauthority
435Thanks Branden for putting together the document so quickly
436Word.
437
438Thomas "Disclaimer" Cox (all opinions mine)
439Question was posed, "how do I show a user the Constitution? How do I display the relevant Ricardian Contract for an action?"
440
441Answer for web clients - the web api that lets you serialize JSON to binary should retrieve the JSON ABI of the command, which contains a section [ricardian clauses] which contains what you need. It'll be ugly as-is, so format it using "handlebar" or "moustache" method
442
443I'm trying to get some sample code to share.
444
445There's a plan to upgrade CLEOS to do this at the command line and show the user the contract.
446
447Roman CryptoLions
448Thomas "Disclaimer" Cox (all opinions mine)
449Summary of testing meeting: 1. All test DEFINITIONS to be entered within 49 minutes of now 2. Links to the data entry forms (2)
450What's the framing of this whole effort?  Is it critical testing before going public with the launch?
451
452Asking because we don't know how to reconcile the hard deadline with continuous testing we've been doing since April in the Jungle Testnet.
453
454Thomas "Disclaimer" Cox (all opinions mine)
455Please focus on critical tests
456
457Denis | EOS Nation
458:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours.
459
460Most of them are not even awake to receive this message, Mao (EOSReal) is still monitoring Telegram and it's 5am for him.
461
462EOS Sillicon Valley also mentioned it would be better if we pushed a couple hours.
463
464:question:PROPOSAL: Have the decision meeting pushed to 0100 UTC Wednesday (June 6)
465
466:+1:/ :-1:for moving +2 hours?
467
468Marc-Antoine Ross - EOS Canadaadmin
469Denis | EOS Nation
470:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours. Most
471:+1:
472
473deck - EOS New York
474Denis | EOS Nation
475:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours. Most
476:+1:
477
478Nate D - Aloha EOS
479Denis | EOS Nation
480:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours. Most
481:+1:
482telegram needs a reaction counter like slack and discord
483
484Branden Espinoza
485Could I get one person to test the forms really quickly?
486
487deck - EOS New York
488Branden Espinoza
489Could I get one person to test the forms really quickly?
490tag
491
492Rick Schlesinger - EOS New York
493Denis | EOS Nation
494:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours. Most
495:+1: @maoyifeng is a good human
496
497Patrick B - Aloha EOS
498Denis | EOS Nation
499:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours. Most
500:+1:
501
502Jose Toriello
503Denis | EOS Nation
504:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours. Most
505:+1:
506
507deck - EOS New York
508Denis | EOS Nation
509:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours. Most
510Tagging @DavidMoss
511
512Sharif Bouktila - EOS Dublinadmin
513@marcantoineross I've made you an Admin here so you can pin next call details.
514
515Marc-Antoine Ross - EOS Canadaadmin
516Sharif Bouktila - EOS Dublin
517@marcantoineross I've made you an Admin here so you can pin next call details.
518Thanks
519
520Denis | EOS Nation
521Rick Schlesinger - EOS New York
522:+1: @maoyifeng is a good human
523[Photo]
524:sleeping:
525
526Thomas "Disclaimer" Cox (all opinions mine)
527Enter your tests!
528https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit?usp=sharing
529
530Google Docs
531EOS UAT - User Acceptance Testing
532Home
533
534
535Create a Case, Record a Test
536Procedure 1: Create a Case
537STEPS
5381, Confirm your case does not yet exist
539a, Click the red Cases tab at the bo...
540
541Rohan - EOSauthority
542Denis | EOS Nation
543:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours. Most
544:+1:I won’t be able to make it, but I feel Asian BPs need to be kept in the loop
545
546Craig Murray - EOS BlockSmith
547Denis | EOS Nation
548:bell:REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours. Most
549:+1:
550
551Thomas "Disclaimer" Cox (all opinions mine)
552@sharifbouktila the 'next validation' call message pinned in this channel is obsolete
553
554Rohan - EOSauthority
555Are we ok to have cleos commands for create steps?
556
557Branden Espinoza
558So long as the procedure to use them is clear to the audience.
559
560deck - EOS New York
561Thomas "Disclaimer" Cox (all opinions mine)
562@sharifbouktila the 'next validation' call message pinned in this channel is obsolete
563@marcantoineross I believe you are admin now
564
565Rohan - EOSauthority
566Branden Espinoza
567So long as the procedure to use them is clear to the audience.
568Ok, something like this 
569> cleos create account ACC_NAME_GENESIS  NEW_ACC  EOS_PUB  EOS_PUB
570
571That should be fairly easy for most people to understand.. the capital letters need to be replaced in..
572
573Branden Espinoza
574Rohan - EOSauthority
575Are we ok to have cleos commands for create steps?
576So long as the procedure to use them is clear to the audience.  The idea is to keep the Steps as process oriented as possible.
577
578Sharif Bouktila - EOS Dublinadmin
579Thomas "Disclaimer" Cox (all opinions mine)
580@sharifbouktila the 'next validation' call message pinned in this channel is obsolete
581@marcantoineross will pin next one,  I won’t make it.
582
583Rohan - EOSauthority
584Branden Espinoza
585So long as the procedure to use them is clear to the audience. The idea is to keep the Steps as process oriented as possible.
586Yes, I like to have ready to execute commands, much easier to compelte them all..
587
588Branden Espinoza
589Rohan - EOSauthority
590Ok, something like this > cleos create account ACC_NAME_GENESIS NEW_ACC EOS_PUB EOS_PUB That should be fairly easy for most
591Out of my world of expertise.
592
593Rohan - EOSauthority
594If we say create an account, its not clear what is being tested.. Specific commands will be easier? I will keep adding it that way.. maybe a note on what it is intended to do followed by the command.
595
596Branden Espinoza
597So long as the procedure to use them is clear to the audience.
598sorry... didn't mean to post that again.
599lol
600I sincerely hope the tool helps.  I'm logging off for about 2 hours. I will check back as soon as I can to address any issues.
601
602Thomas "Disclaimer" Cox (all opinions mine)
603Testing Zoom call in 5 minutes, at 21:35 UTC
604https://zoom.us/j/5788946547
605
606Zoom Video
607Join our Cloud HD Video Meeting now
608Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
609Folks engaged in testing, please hop on -- I have a question from Bart and Arhag about the testing method, there's a concern that certain approaches might create spurious errors
610
611deck - EOS New York
612Thomas "Disclaimer" Cox (all opinions mine)
613Testing Zoom call in 5 minutes, at 21:35 UTC https://zoom.us/j/5788946547
614@abourget @michaelyeates @ eric
615
616Roman CryptoLions
617@xebb82
618
619deck - EOS New York
620Roman CryptoLions
621@xebb82
622yea that one haha
623
624Roman CryptoLions
625:blush:
626
627deck - EOS New York
628@igorls
629Marc-Antoine Ross - EOS Canada pinned « Enter your tests! https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit?usp=sharing»
630
631Sam - EOS Dublin
632Are we all in agreement that we are moving THE CALL from 2300 UTC to 0100 UTC? I haven't seen any objections yet.
633
634Gustavo Mick - EOS Argentina
635Eos argentina agrees
636
637David Moss
6389am Wednesday China time. Definitely want Asia to participate here
639
640Branden Espinoza
641After you submit a case, you are taken to a page that includes a link to edit your case.   You should bookmark that link for each case since it is the only means you have to edit a case once it is submitted.
642
643James Sutherland - Cypherglass.com
644Sam - EOS Dublin
645Are we all in agreement that we are moving THE CALL from 2300 UTC to 0100 UTC? I haven't seen any objections yet.
646Works for me.  Please pin that if it's for real.
647If it becomes real I mean
648
649Marc-Antoine Ross - EOS Canadaadmin
650ALL: Next zoom call at 0100UTC to review test results and agree on plan
651Marc-Antoine Ross - EOS Canada pinned «ALL: Next zoom call at 0100UTC to review test results and agree on plan»
652
653James Sutherland - Cypherglass.com
654Marc-Antoine Ross - EOS Canada
655ALL: Next zoom call at 0100UTC to review test results and agree on plan
656+1
657
658mini - EOS Argentina
659Sam - EOS Dublin
660Are we all in agreement that we are moving THE CALL from 2300 UTC to 0100 UTC? I haven't seen any objections yet.
661+1
662
663deck - EOS New York
664Validation call with Aarin Hagerty(edited for correct spelling)
665
666Pausing the chain is dangerous because there a potential to fork, if keys are shared and/or we have a rogue ABP. After 15%, everyone can fix a checkpoint at the first schedule, making that key irrelevant for eternity.
667
668Having defined process for injection and validation on a testnet is sufficient to get high degree of confidence that a mainnet using the same process, validation being rerun, is good.
669
670Two options:
671Throw all current mainnet candidates out after testing is complete and recreate using the deterministic approaches we have. We would validate the boot sequence and the state right after. (recommended) 
672Reuse the chain we have been testing and allow this potential issue to remain 
673
674Testing delayed transactions would be interesting.
675
676Stuardo Rodríguez 🇬🇹
677Throw all current mainnet candidates out after testing is complete and recreate using the deterministic approaches we have. 
678<- :clap::clap::clap::clap::clap::clap::clap:
679that would throw all "ego"  away about any opinion of bios/gb chain, and launch a unified mainnet together.
680
681Thomas "Disclaimer" Cox (all opinions mine)
682deck - EOS New York
683Validation call with Aarin Hagerty(edited for correct spelling) Pausing the chain is dangerous because there a potential to for
684Arhag, often goes by Aarin Hagerty, various spellings. Github is "https://github.com/arhag"
685
686GitHub
687arhag
688arhag has 11 repositories available. Follow their code on GitHub.
689Please enter test results!
690Please enter test results!
691Please enter test results!
692https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit#gid=1501553294
693
694Google Docs
695EOS UAT - User Acceptance Testing
696Home
697
698
699Create a Case, Record a Test
700Procedure 1: Create a Case
701STEPS
7021, Confirm your case does not yet exist
703a, Click the red Cases tab at the bo...
704
705Nathan Rempel | GenerEOS Sydney
706deck - EOS New York
707Validation call with Aarin Hagerty(edited for correct spelling) Pausing the chain is dangerous because there a potential to for
708Honestly I thought this was all done during all those dry runs everyone was doing, but can't turn back the clock now. I agree if we're happy with acceptance testing and have an agreed validation test, it makes sense if the code hasn't changed, re-start, validate, open tx
709
710deck - EOS New York
711The 'nice' thing about restarting the chain is it gives us the oppurtunity to decided on the method of paying for RAM at launch. One group or the other can launch, freeze for N hours, allow for everyone to mesh, validate (much like the snapshot), and report results. It might just work out :)
712
713Timothy Lewis
714deck - EOS New York
715The 'nice' thing about restarting the chain is it gives us the oppurtunity to decided on the method of paying for RAM at launch.
716+1
717
718Craig Murray - EOS BlockSmith
719we already have one ready for tx though, why does that need restarted?
720
721Nathan Rempel | GenerEOS Sydney
722Craig Murray - EOS BlockSmith
723we already have one ready for tx though, why does that need restarted?
724Have we run the UAT against a copy of that chain?
725
726Timothy Lewis
727Have we had a well done voting tool at all during this?
728
729Nathan Rempel | GenerEOS Sydney
730deck - EOS New York
731The 'nice' thing about restarting the chain is it gives us the oppurtunity to decided on the method of paying for RAM at launch.
732Just need to make sure we tighten up the timelines
733like, UAT is done, we have 2 hours to boot, 2 hours to validate, if everyone checks in good, send it
734
735deck - EOS New York
736Timothy Lewis
737Have we had a well done voting tool at all during this?
738I believe that eosportal was tested against a Core testnet
739
740Thomas "Disclaimer" Cox (all opinions mine)
741Only 13 test cases added so far. 
742ZERO test results added so far.
743Please pick up the pace.
744
745Nathan Rempel | GenerEOS Sydney
746Can i throw some of the latest firestarter results in here i should ido that elsewhere?
747
748Thomas "Disclaimer" Cox (all opinions mine)
749Nathan Rempel | GenerEOS Sydney
750Can i throw some of the latest firestarter results in here i should ido that elsewhere?
751check your PMs
752
753mini - EOS Argentina
754Thomas "Disclaimer" Cox (all opinions mine)
755Only 13 test cases added so far. ZERO test results added so far. Please pick up the pace.
756@zhaoyu did some testing, dont know if they put it in the sheet, but they have already test a lot of things.
757
758Craig Murray - EOS BlockSmith
759yeah the chain B has 2.5 days of testing already, there was a spreadsheet for that, not sure what happened to all that :cry:
760
761Nathan Rempel | GenerEOS Sydney
762Does the DaoMao test incude any/many/all of those 13 cases?
763
764Thomas "Disclaimer" Cox (all opinions mine)
765Craig Murray - EOS BlockSmith
766yeah the chain B has 2.5 days of testing already, there was a spreadsheet for that, not sure what happened to all that :cry:
767If you can find it, paste the link in to the test results form. No reinventing wheels here please
768mini - EOS Argentina
769@zhaoyu did some testing, dont know if they put it in the sheet, but they have already test a lot of things.
770They may not know about the form yet.
771
772mini - EOS Argentina
773https://github.com/eoslaomao/eos-cluster-generator
774
775GitHub
776EOSLaoMao/eos-cluster-generator
777Contribute to eos-cluster-generator development by creating an account on GitHub.
778
779Craig Murray - EOS BlockSmith
780Dublin would know they were doing all the record keeping.  I'm fighting with this private network wireguard mesh situation trying to find the correct fork for each of my nodes
781
782mini - EOS Argentina
783Conclusion
784
7851     The voting works as expected.
7862  The delegatebw and undelegatebw works as expected.
7873   The network needs to reach 15% votings, until then, you cannot unstake all tokens.
7884    staked tokens weather be used for voting or not, both can be unstaked after 15% voting readched.
789from their repo
790
791Thomas "Disclaimer" Cox (all opinions mine)
792mini - EOS Argentina
793Conclusion 1 The voting works as expected. 2 The delegatebw and undelegatebw works as expected. 3 The network needs to r
794Outstanding. Please PM me the link to their repo
795
796mini - EOS Argentina
797Thomas "Disclaimer" Cox (all opinions mine)
798They may not know about the form yet.
799yes probably
800
801Nathan Rempel | GenerEOS Sydney
802how quickly can someone update https://github.com/eoslaomao/eos-cluster-generator to cover the remaning UATs?
803
804GitHub
805EOSLaoMao/eos-cluster-generator
806Contribute to eos-cluster-generator development by creating an account on GitHub.
807i can start writing an eosjs for the non-time sensitive test cases too if no one has yet, or are we running manual commands?
808
809mao EOSREAL
810chinese bpcs confirming the call 1.5 hours ahead and are discussing their stands.
811
812Jose Toriello
813mao EOSREAL
814chinese bpcs confirming the call 1.5 hours ahead and are discussing their stands.
815Please specify what time you mean?
816
817Nathan Rempel | GenerEOS Sydney
818I'm currently writing a supplment document with all the cleos commands to run to match the test cases and what the expected results should be
819BPs can manually run them if they wish and add to the form
820
821mao EOSREAL
822Jose Toriello
823Please specify what time you mean?
824Roughly 1.5 hours ahead. 9pm est.
825
826WinLin-EOSBIXIN
827Marc-Antoine Ross - EOS Canada
828Just to recap my recommendation: A) We continuously improve security of the network (multiple initiatives going on now to hel
829:+1:
830Thomas "Disclaimer" Cox (all opinions mine)
831Arhag, often goes by Aarin Hagerty, various spellings. Github is "https://github.com/arhag"
832to be honest most case in the execel doc, many of Chinese BPs have finished since Dawn-v4.2  and many times test in v1.0.1
833
834Nathan Rempel | GenerEOS Sydney
835The UAT document seems a little schewed, like Case RAM market has name bidding..
836Ok guys here's a supplement document: https://docs.google.com/document/d/1qFEUt3Z-sy8-vWrzmoH-TjXE6850_4lCpdzBoDaj4A0/edit?usp=sharing
837
838Google Docs
839EOS UAT - Commands
840CA001 Run: cleos -u system newaccount --stake-net "1.0000 EOS" --stake-cpu "1.0000 EOS" --buy-ram-kbytes 8 -p Verify: cleos -u get account Sh...
841This is so individual BPs or "anyone" can run the UAT tests by command line. Please continue to add commands for each test case as appropriate
842some of the latest UATs will require scripts to be run, however I see several are from @BohdanCryptoLions
843If @BohdanCryptoLions has been running against release-rc or v1.0.1 perhaps you can publish those results
844
845mini - EOS Argentina
846awesome work!
847Nate D - Aloha EOS invited Peter Bue | EOSAmericas
848Peter Bue | EOSAmericas invited Ed Silva
849
850Thomas "Disclaimer" Cox (all opinions mine)
851mao EOSREAL
852chinese bpcs confirming the call 1.5 hours ahead and are discussing their stands.
853:+1::grin:
854Nathan Rempel | GenerEOS Sydney
855I'm currently writing a supplment document with all the cleos commands to run to match the test cases and what the expected resu
856:+1::grin::heart:
857WinLin-EOSBIXIN
858to be honest most case in the execel doc, many of Chinese BPs have finished since Dawn-v4.2 and many times test in v1.0.1
859Wonderful.
860
861WinLin-EOSBIXIN
862Thomas "Disclaimer" Cox (all opinions mine)
863Wonderful.
864yes, Asia bp teams have done lots things but someone always choose to ignore this
865this is unfair
866
867Nathan Rempel | GenerEOS Sydney
868WinLin-EOSBIXIN
869yes, Asia bp teams have done lots things but someone always choose to ignore this
870I don't think the community is ignoring, do you have documentation that test was run? Please, PLEASE share!
871
872Thomas "Disclaimer" Cox (all opinions mine)
873WinLin-EOSBIXIN
874yes, Asia bp teams have done lots things but someone always choose to ignore this
875I don't think it's ignoring, so much as cluelessness. I hang my head in shame
876
877WinLin-EOSBIXIN
878thanks all
879the validation tool :https://github.com/EOSBIXIN/eostoolkit/tree/master/eos_validator
880
881GitHub
882EOSBIXIN/eostoolkit
883Contribute to eostoolkit development by creating an account on GitHub.
884this tool support eos-bios and manula startup chain
885both
886
887Nathan Rempel | GenerEOS Sydney
888for all the chinese BP that have used this tool, do you have a document showing the output?
889
890Syed Jafri | EOS Cafe / Calgary
891Yes it would be great to see validation from Asia
892So we can record that
893Right now, its only BIXIN and a handful that we have seen
894
895WinLin-EOSBIXIN
896[Photo]
897like this
898
899Syed Jafri | EOS Cafe / Calgary
900
901WinLin-EOSBIXIN
902Photo
903That is run by you though
904We mean other Asian BPCs
905
906WinLin-EOSBIXIN
907[Photo]
908wait please, it is too early I will find some bp to prove
909@zhaoyu from EOSLAOMAO
910@Joshuaqiu from ESOSeco
911@dftle from eosAsia
912
913Syed Jafri | EOS Cafe / Calgary
914Yes we have those 3, they are vocal in calls as well
915We were wondering if theres anyone else
916We have missed?
917
918Alexandre Bourget - EOS Canada
919WinLin was the first to write a validation tool, first to publish reports and I think he has the most complete validation took to date.
920
921He published his results time and time again and helped identify issues in the first 3 iterations of a mainnet candidate.
922
923I am truly grateful for your work WinLin
924
925Nathan Rempel | GenerEOS Sydney
926Alexandre Bourget - EOS Canada
927WinLin was the first to write a validation tool, first to publish reports and I think he has the most complete validation took t
928:+1::+1::+1:
929
930WinLin-EOSBIXIN
931we all support EOS and want to make her more valueable, so let's move on and introdcue her into the world
932
933Luke Stokes
934Has anyone else created a currency contract yet? I tried created the eosDAC one on Jungle and it blew up. Might just be our contract is bad, but I wanted to ask here before I ask in Jungle.
935
936Nate D - Aloha EOS
937WinLin-EOSBIXIN
938we all support EOS and want to make her more valueable, so let's move on and introdcue her into the world
939:+1:
940
941WinLin-EOSBIXIN
942Luke Stokes
943Has anyone else created a currency contract yet? I tried created the eosDAC one on Jungle and it blew up. Might just be our cont
944yes, I have created some token in dawn v-4.2
945
946Peter Bue | EOSAmericas
947WinLin-EOSBIXIN
948we all support EOS and want to make her more valueable, so let's move on and introdcue her into the world
949:+1::+1:
950
951WinLin-EOSBIXIN
952so there should be some wrong in you env,please chekc again
953
954Luke Stokes
955WinLin-EOSBIXIN
956yes, I have created some token in dawn v-4.2
957Thanks. I'll dig into main.cpp at line 2584 to see what's broken. 🙂
958I had an earlier issue with boost, so it surely could be my local env. Thanks.
959
960Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer
961WinLin-EOSBIXIN
962wait please, it is too early I will find some bp to prove
963Tyee from EOSpace
964
965Nathan Rempel | GenerEOS Sydney
966Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer
967Tyee from EOSpace
968:+1:
969
970WinLin-EOSBIXIN
971Luke Stokes
972Thanks. I'll dig into main.cpp at line 2584 to see what's broken. 🙂
973you can take a look about the EOSLaoMao tool:https://github.com/EOSLaoMao/eos-cluster-generator
974
975GitHub
976EOSLaoMao/eos-cluster-generator
977Contribute to eos-cluster-generator development by creating an account on GitHub.
978
979Luke Stokes
980thanks. I haven't played with that yet, but it looks really interesting
981
982WinLin-EOSBIXIN
983yes, that's  very intreasting
984Gordo | HelloEOS joined group via invite link
985
986Branden Espinoza
987Many of you know my role in this. Is there any value in me attending the next zoom call?
988Maybe a better question for @thomasbcox
989
990Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer
991Luke Stokes
992thanks. I haven't played with that yet, but it looks really interesting
993You can use this tool to validate yourself.
994
995Thomas "Disclaimer" Cox (all opinions mine)
996Branden Espinoza
997Many of you know my role in this. Is there any value in me attending the next zoom call?
998No
999
1000Joshua Qiu @EOSeco
1001Syed Jafri | EOS Cafe / Calgary
1002Right now, its only BIXIN and a handful that we have seen
1003i have another , but only check balance
1004
1005Branden Espinoza
1006Thomas "Disclaimer" Cox (all opinions mine)
1007No
1008TY.
1009
1010Gordo | HelloEOS
1011WinLin-EOSBIXIN
1012wait please, it is too early I will find some bp to prove
1013We've been using WinLin's tool to do the validation
1014
1015Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer
1016Joshua Qiu @EOSeco
1017i have another , but only check balance
1018That's fine. You can use your own tool to validate both chains.
1019
1020Joshua Qiu @EOSeco
1021https://github.com/qiushaoxi/eos-validation snapshot balance are fine on both side
1022
1023GitHub
1024qiushaoxi/eos-validation
1025Contribute to eos-validation development by creating an account on GitHub.
1026
1027Nathan Rempel | GenerEOS Sydney
1028Ok guys, in advance of this call I have created a survey so we can get some "real documented concensus" rather than everyone speaking up in a call
1029https://goo.gl/forms/D8M7c5QFyMCwmCaF2
1030
1031Google Docs
1032BP Launch Survey
1033No / No Combination with no explanation will be rejected.
1034Provide telegram handle so we can confirm you represent your BP
1035I'd appreciate if someone could review it quickly if there's anything that should be added
1036
1037deck - EOS New York
1038I believe the suggested time to launch was tomorrow at 1300 utc
1039
1040Nathan Rempel | GenerEOS Sydney
1041oops my bad
1042
1043deck - EOS New York
1044np good work putting this together
1045
1046Syed Jafri | EOS Cafe / Calgary
1047I dont think we can reverse chain probably, do you mean load from backup?
1048
1049Nathan Rempel | GenerEOS Sydney
1050mixing up my time zone
1051
1052deck - EOS New York
1053@marcantoineross Can you post the zoom link
1054
1055Marc-Antoine Ross - EOS Canadaadmin
1056All, here the proposed flow for the call
1057
1058A) We continuously improve security of the network (multiple initiatives going on now to help, thanks to @trustlayer @dftle) 
1059 
1060In parallel: 
10611. We agree on the optimal boot sequence (is RAM buying the only issue to solve?) 
10622. We code it (if not already done) and review open source implementation 
10633. We inject it (if not already done) on a swarm of nodes that includes everyone 
10644. We test it (insert Thomas' test report spreadsheet here) 
10655. We select an ABP to hold custody of the network until the 15% vote is done 
10666. We make sure we are all meshed together and help hide the ABP 
1067
1068https://zoom.us/j/681388230
1069
1070Zoom Video
1071Join our Cloud HD Video Meeting now
1072Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
1073Marc-Antoine Ross - EOS Canada pinned « All, here the proposed flow for the call A) We continuously improve security of the network (multiple initiatives going on now »
1074
1075Nathan Rempel | GenerEOS Sydney
1076Syed Jafri | EOS Cafe / Calgary
1077I dont think we can reverse chain probably, do you mean load from backup?
1078Yes
1079basically "restart"
1080
1081Timothy Lewis
1082Guys the call is at max participants
1083
1084Denis | EOS Nation
1085🤔 I'll let people know about this
1086
1087Craig Murray - EOS BlockSmith
1088i thought someone with a 200 max was going to create?
1089
1090Nathan Rempel | GenerEOS Sydney
1091Timothy Lewis
1092Guys the call is at max participants
1093Are we having 1 BP rep in the call? I know there is a lot of BP candidates
1094
1095Timothy Lewis
1096No one from my team is in the call and I would like to be.
1097
1098Andrey Marchuk
1099there are 2 spots
1100
1101Nathan Rempel | GenerEOS Sydney
1102they are working to expand to 200
1103
1104Andrey Marchuk
1105try now
1106
1107Nathan Rempel | GenerEOS Sydney
1108some open spaces now
1109
1110Timothy Lewis
1111sweet
1112ty
1113
1114James Sutherland - Cypherglass.com
1115200 people allowed now
1116Nice job @marcantoineross !
1117
1118Denis | EOS Nation
1119:man::woman::girl::girl: more people allowed!
1120
1121James Sutherland - Cypherglass.com
1122Please mute yourself
1123Stay muted until you need to speak
1124Mr Fox invited Jialin Li - EOS WTZ
1125
1126Alex - EOS SOCAL
1127Did the call just die?
1128
1129Nathan Rempel | GenerEOS Sydney
1130non
1131
1132James Sutherland - Cypherglass.com
1133I am still on
1134138 people connected
1135
1136deck - EOS New York
1137@marcantoineross do it
1138I vote @marcantoineross
1139
1140Alexandre Bourget - EOS Canada
1141Great call tonight folks
1142
1143Gustavo Mick - EOS Argentina
1144@abourget could you summarize results from the meeting, thanks
1145
1146Nathan Rempel | GenerEOS Sydney
1147Can we get a group made for the Asian security audit coordination asap
1148
1149Thomas "Disclaimer" Cox (all opinions mine)
1150Remarkably productive, all things considered. Many thanks to @marcantoineross for hosting
1151
1152mini - EOS Argentina
1153Nathan Rempel | GenerEOS Sydney
1154Can we get a group made for the Asian security audit coordination asap
1155+1 to this
1156
1157Nathan Rempel | GenerEOS Sydney
1158@bo_eossv
1159
1160Syed Jafri | EOS Cafe / Calgary
1161@eosnewyork, we also need a global statement for this security delay
1162Nathan Rempel | GenerEOS Sydney invited Bo - EOS Silicon Valley
1163
1164Gustavo Mick - EOS Argentina
1165We need a summary of the meeting for those who have not been able to be there.
1166
1167Chitty 🅑 - EOS Argentina
1168Did I understand correctly that EOS BIOS will launch and EOS Core will appoint the ABPs... right?
1169
1170Andrey Marchuk
1171productive call, thank you!
1172
1173Nathan Rempel | GenerEOS Sydney
1174Chitty 🅑 - EOS Argentina
1175Did I understand correctly that EOS BIOS will launch and EOS Core will appoint the ABPs... right?
1176No..?
1177what do you mean appoint?
1178
1179Chitty 🅑 - EOS Argentina
1180mmm, I guess we will wait for the votes to be counted.. I believe the question was 
1181SHOULD WE RESTART A NEW CHAIN, INJECTED WITH THE CURRENT 579a CONTENTS. AND HAVE GHOSTBUSTER RUN ABP TO 15% UNLOCK ?
1182
1183Nathan Rempel | GenerEOS Sydney
1184i thought that question was discarded
1185
1186Chitty 🅑 - EOS Argentina
1187Nathan Rempel | GenerEOS Sydney
1188i thought that question was discarded
1189why?
1190
1191Craig Murray - EOS BlockSmith
1192because JEM declined on behalf of ghostbusters to do so, he was not particularly interested in that
1193
1194Chitty 🅑 - EOS Argentina
1195Did Jem represent all of Ghostbuster?
1196
1197Syed Jafri | EOS Cafe / Calgary
1198I believe the final was for everyone to join 579a chain once it passes security check phase
1199
1200Craig Murray - EOS BlockSmith
1201Syed Jafri | EOS Cafe / Calgary
1202I believe the final was for everyone to join 579a chain once it passes security check phase
1203Yes, 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.
1204
1205Syed Jafri | EOS Cafe / Calgary
1206They offerred to join as every other BPC
1207
1208Craig Murray - EOS BlockSmith
1209yes, they offered to join as ordinary BPCs and not be the ABP
1210
1211Bo - EOS Silicon Valley
1212Sure!
1213
1214Chitty 🅑 - EOS Argentina
1215Ok, I must have missed that.. will wait on the report
1216
1217Luke Stokes
1218Chitty 🅑 - EOS Argentina
1219Did Jem represent all of Ghostbuster?
1220One person representing multiple BPCs seemed counter to DPOS to me, but I'm glad we worked through things and got consensus. Great meeting.
1221
1222Syed Jafri | EOS Cafe / Calgary
1223Luke Stokes
1224One person representing multiple BPCs seemed counter to DPOS to me, but I'm glad we worked through things and got consensus. Gre
1225You mean proxying votes is counter to DPOS?
1226Thats a first
1227They delegated their votes
1228
1229Luke Stokes
1230No, proxy is fine if it's on chain and known
1231
1232Nathan Rempel | GenerEOS Sydney
1233Luke Stokes
1234One person representing multiple BPCs seemed counter to DPOS to me, but I'm glad we worked through things and got consensus. Gre
1235I 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
1236Nathan Rempel | GenerEOS Sydney invited Hugo Yang - EOS Silicon Valley
1237
1238David P - EOS42
1239Luke Stokes
1240One person representing multiple BPCs seemed counter to DPOS to me, but I'm glad we worked through things and got consensus. Gre
1241Given the timezone of the vote, a proxy representative makes sense in the same way Bo was for multiple BP's
1242
1243Luke Stokes
1244Thanks for clarifying that's an arangement (via proxy) people are comfortable with
1245
1246Igor Lins e Silva - EOS Rio
1247Just 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
1248
1249Nathan Rempel | GenerEOS Sydney
1250@bo_eossv @hugo_eossv Is there a testnet already existing or do you need the community to start one?
1251
1252Syed Jafri | EOS Cafe / Calgary
1253could we use jungle?
1254
1255Igor Lins e Silva - EOS Rio
1256Syed Jafri | EOS Cafe / Calgary
1257could we use jungle?
1258+1
1259
1260Nathan Rempel | GenerEOS Sydney
1261Well, I thought the idea would be to run it against a clone of our candidate
1262but as long as the code is the code
1263🤷‍♂️
1264I 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
1265
1266Nate D - Aloha EOS
1267I thought the idea was to start one on production infrastructure
1268But yes, needs clarification.
1269
1270Nathan Rempel | GenerEOS Sydney
1271Nate D - Aloha EOS
1272I thought the idea was to start one on production infrastructure
1273That was my understanding also, so Im eager to swtich our production over to this test
1274Nathan Rempel | GenerEOS Sydney invited Dr Ye EOS WashingtonDC - TChain
1275
1276Bo - EOS Silicon Valley
1277Let me do a quick check
1278
1279Mr Fox
1280Bo - EOS Silicon Valley
1281Let me do a quick check
1282:+1:
1283Mr Fox invited Xueyuan She_EOS_WTZ
1284
1285Stuardo Rodríguez 🇬🇹
1286Nathan Rempel | GenerEOS Sydney
1287I 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
1288+1
1289
1290Nathan Rempel | GenerEOS Sydney
1291Is someone already preparing a joint statement to the community regarding the eosio issuance of tokens to gift the genesis accounts with free ram?
1292
1293Syed Jafri | EOS Cafe / Calgary
1294Nathan Rempel | GenerEOS Sydney
1295Is someone already preparing a joint statement to the community regarding the eosio issuance of tokens to gift the genesis accou
1296Cypherglass offered to do a video
1297@finchify
1298
1299Nathan Rempel | GenerEOS Sydney
1300It would be great if we could get a joint steemit/etc to include and share the video
1301Dr Ye EOS WashingtonDC - TChain
1302Just 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
1303
1304Dafeng Guo - EOS Asia
1305Nathan Rempel | GenerEOS Sydney
1306I 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
1307Details will be coming out soon. Things are rolling.
1308
1309Nathan Rempel | GenerEOS Sydney
1310Dafeng Guo - EOS Asia
1311Details will be coming out soon. Things are rolling.
1312Thanks for that
1313
1314Syed Jafri | EOS Cafe / Calgary
1315Dafeng Guo - EOS Asia
1316Details will be coming out soon. Things are rolling.
1317Thanks Dafeng, keep us updated!
1318
1319Bo - EOS Silicon Valley
1320Dafeng Guo - EOS Asia
1321Details will be coming out soon. Things are rolling.
1322:+1::+1:
1323Dr Ye EOS WashingtonDC - TChain
1324Nathan Rempel | GenerEOS Sydney
1325Can we get a group made for the Asian security audit coordination asap
1326please get tchain posted
1327
1328Kevin Rose - EOS New York
1329Syed Jafri | EOS Cafe / Calgary
1330@eosnewyork, we also need a global statement for this security delay
1331We’ve already issued it
1332The statement today states the time needed
1333https://steemit.com/eos/@eosnewyork/the-eos-mainnet-launch-security-and-software-testing
1334
1335Steemit
1336The EOS Mainnet Launch: Security & Software Testing — Steemit
1337Disclaimer: As a token holder, it is important that you do nothing during this period. Never expose your private key… by eosnewyork
1338
1339Dafeng Guo - EOS Asia
1340Igor Lins e Silva - EOS Rio
1341+1
1342Are 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.
1343
1344Timothy Lewis
1345Kevin Rose - EOS New York
1346https://steemit.com/eos/@eosnewyork/the-eos-mainnet-launch-security-and-software-testing
1347Great post.
1348
1349Syed Jafri | EOS Cafe / Calgary
1350I 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
1351Would be nice to reach out to him @BohdanCryptoLions
1352
1353Kevin Rose - EOS New York
1354Timothy Lewis
1355Great post.
1356Group effort. Thanks Tim. If you haven’t posted already please feel free to. This is a statement meant to represent us all.
1357
1358Nathan Rempel | GenerEOS Sydney
1359Syed Jafri | EOS Cafe / Calgary
1360I think Bohdan has one of the most experience in the community for launching testnets. He is also a relatively neutral party tha
1361+1
1362
1363Jose Toriello
1364+1+1
1365Timothy Lewis
1366Great post.
1367+1
1368
1369Luke Stokes
1370Kevin Rose - EOS New York
1371The statement today states the time needed
1372I was thinking the same thing. That post covered what we ended up deciding on the call quite nicely. Well done!
1373Dr Ye EOS WashingtonDC - TChain
1374Syed Jafri | EOS Cafe / Calgary
1375I think Bohdan has one of the most experience in the community for launching testnets. He is also a relatively neutral party tha
1376+1 happy to help if he Bohdan agrees to take the job
1377
1378Nathan Rempel | GenerEOS Sydney
1379Any other candidates to spin up this testnet if @BohdanCryptoLions isn't available?
1380
1381mini - EOS Argentina
1382I think eos.host was quite good, dont know if those guys are up for it
1383the monitor was superv, and they have account creation and a super nice voting system
1384
1385Dafeng Guo - EOS Asia
1386I contacted EOS.host yesterday
1387They are happy to help
1388
1389Craig Murray - EOS BlockSmith
1390Kevin Rose - EOS New York
1391https://steemit.com/eos/@eosnewyork/the-eos-mainnet-launch-security-and-software-testing
1392nice job staying away from calling out these launch cohorts by name.  Well done sir, thanks
1393
1394mini - EOS Argentina
1395Dafeng Guo - EOS Asia
1396They are happy to help
1397great!
1398
1399Crystal Rose | :zap:SENSE | :purple_heart:shEOS
1400Throwing 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:
1401
1402Branden Espinoza
1403Crystal Rose | :zap:SENSE | :purple_heart:shEOS
1404Throwing out some gratitude and kudos to everyone for working hard and giving yourself to this mission. It’s apparent how much t
1405I 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.
1406
1407Bo - EOS Silicon Valley
1408Thanks so much everyone for making EOS possible! Really appreciate it:+1:
1409We 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!
1410
1411Patrick B - Aloha EOS
1412Bo - EOS Silicon Valley
1413Thanks so much everyone for making EOS possible! Really appreciate it:+1:
1414Thanks to you as well Bo!
1415Mark-eosantpool invited Mr.Z
1416
1417Marc-Antoine Ross - EOS Canadaadmin
1418All, 
1419
1420Thanks for the productive call. 
1421
1422Find below the minutes, if you find anything not accurate, please suggest/comment and we will fix.
1423The raw log is included at the bottom of the document.
1424
1425https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c
1426
1427Next steps:
1428June 6, 1300 UTC: to get consensus on remaining points not covered yet
1429    Test plan & timeline
1430    ABP selection
1431    Meshing and ABP protection
1432    More?
1433June 7, 0100 UTC: the next go/no go discussion, hopefully with the initial security report in hand
1434
1435Thanks, good after-mor-night!
1436
1437Google Docs
1438GoNoGo Call
1439Wednesday 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...
1440Marc-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»
1441
1442Daniel Larimer
1443David Moss
1444All but .1337 of one EOS token has been accounted for...
1445That’s 1337.
1446
1447David Moss
1448Ah, interesting. I heard it different.
1449Still, a rounding error.
1450Printing tokens for RAM startup is a rounding error as well.
1451
1452Timothy Lewis
1453@abourget @marcantoineross did anyone try to implement the RAM cost solution from K Kim of EOSeoul?
1454https://gist.github.com/redjade/c22b2d7fcab068af67c0de31724eb710
1455diff for adding mitigatebiosramcost on eosio 1.0
1456[Photo]
1457
1458Zhao Yu@ EOSLaoMao.com
1459any post about the whole idea?
1460
1461Timothy Lewis
1462From the authoer @resvera: "It compiles well. I didn’t test it. I’m not quite expert on boot sequences. But a developer.
1463
1464test 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. 
1465
1466This action is very delicate one. Test should include code reviews and actual push action test."
1467
1468Jose Toriello
1469David Moss
1470Printing tokens for RAM startup is a rounding error as well.
1471I suggest "issuing" and not "printing" as a better vocabulary, especially given the sensitivity around the subject.
1472
1473James Sutherland - Cypherglass.com
1474Marc-Antoine Ross - EOS Canada
1475All, Thanks for the productive call. Find below the minutes, if you find anything not accurate, please suggest/comment and w
1476Nice work on this.  Thanks for taking the effort to put this document togeather.
1477
1478Jose Toriello
1479Crystal Rose | :zap:SENSE | :purple_heart:shEOS
1480Throwing out some gratitude and kudos to everyone for working hard and giving yourself to this mission. It’s apparent how much t
1481+1
1482Branden Espinoza
1483I am too. I made the mistake of sticking my nose into some social media crypto groups today. They have no idea. The disconnec
1484+1
1485Marc-Antoine Ross - EOS Canada
1486All, Thanks for the productive call. Find below the minutes, if you find anything not accurate, please suggest/comment and w
1487+1
1488
1489Timothy Lewis
1490Jose Toriello
1491I suggest "issuing" and not "printing" as a better vocabulary, especially given the sensitivity around the subject.
1492There 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?
1493
1494David Moss
1495I agree it's a good solution. Would it require restarting the mainnet candidate>?
1496
1497Timothy Lewis
1498It would require a code review first, and then a test.
1499
1500Nathan Rempel | GenerEOS Sydney
1501Question 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
1502
1503Timothy Lewis
1504If the test was successful then we would have the opportunity to walk through the boot process as a community.
1505
1506Nathan Rempel | GenerEOS Sydney
1507Timothy Lewis
1508If the test was successful then we would have the opportunity to walk through the boot process as a community.
1509Have you run his code and tested it?
1510
1511Timothy Lewis
1512We are talking about 2-3 hours to complete a test. I have not run it. It needs to be tested.
1513I 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.
1514
1515Marc-Antoine Ross - EOS Canadaadmin
1516Timothy Lewis
1517I 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
1518While 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.
1519
1520Nathan Rempel | GenerEOS Sydney
1521Yes, 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
1522Otherwise we're in an endless loop of "hey what about this?"
1523
1524Timothy Lewis
1525Understood. I am now just trying to find out if anyone had tested it, or reasons they anyone may have not wanted to.
1526
1527Nathan Rempel | GenerEOS Sydney
1528Timothy Lewis
1529Understood. I am now just trying to find out if anyone had tested it, or reasons they anyone may have not wanted to.
1530Looking at the code my concern is that while it may be valid its a lot of change
1531Considering validation tools already check every account balance i think something simpler like
1532 
1533void token::unissue(quantity){
1534statstable.modify( st, 0, [&]( auto& s ) {
1535       s.supply -= quantity;
1536    });
1537}
1538
1539would be preferable in the eosio.token contract, then reconfirm balances = total supply
1540Above is obviously invalid code, just making a point
1541That said I agree with using tools that don't require contract changes... and burning the inflation through those pre-exisisting tools, personally
1542Emily Bush - shEOS invited Autumn Moss Penaloza / shEOS
1543
1544Yvonne (EOShenzhen)
1545Kevin Rose - EOS New York
1546We’ve already issued it
1547great.thank you
1548
1549Nathan Rempel | GenerEOS Sydney
1550I guess its getting late in North America, but Europe is starting to wake up, looking forward to some updates soon :)
1551
1552Luke Stokes
1553Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer
1554You can use this tool to validate yourself.
1555Is 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
1556
1557Sandwich
1558Joshua Qiu @EOSeco
1559you dont do any thing with snapshot_unregistered.csv?
1560https://github.com/EOSIO/eos/pull/2669/files ?
1561GitHub
1562Draft of eosio.unregd to keep unreg'd Ethereum addr + EOS balances on chain by a...
1563The 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...
1564
1565WinLin-EOSBIXIN
1566Luke Stokes
1567Is there a better place to discuss this tool? I had a question about why eosiocpp was removed. I can't compile my token contract
1568you can not find you eosiocpp?
1569maybe sudo make install again
1570
1571Nathan Rempel | GenerEOS Sydney
1572Any news guys?
1573
1574Sharif Bouktila - EOS Dublinadmin
1575Next call is 13:00 UTC 6th June 2018
1576
1577I’ll post Zoom details before here.
1578
1579Ross (EOSphere)
1580Would 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
1581
1582Google Docs
1583EOS UAT - User Acceptance Testing
1584Home
1585
1586
1587Create a Case, Record a Test
1588Procedure 1: Create a Case
1589STEPS
15901, Confirm your case does not yet exist
1591a, Click the red Cases tab at the bo...
1592
1593jem
1594Account creation RAM costs solution
1595
1596We 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.
1597
1598During 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.
1599
1600Just 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.
1601
1602By 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.
1603
1604We believe that this simple process is the correct way to create user accounts while maintaining precise suply of total EOS tokens.
1605
1606Sharif Bouktila - EOS Dublinadmin
1607EVERYONE - We have our next Validation Call at 13:00 UTC 
1608
1609If you are not directly involved in testing / validation, you do not need to attend the call. 
1610
1611The focus on this call with be establishing what the current status is. 
1612
1613Agreeing what the focus is for the next 6 hours. 
1614
1615@samnoble or I will post clear minutes and actions to this group for awareness so nothing is lost in translation.
1616
1617mao EOSREAL
1618jem
1619Account creation RAM costs solution We have a total solution for RAM allocation, which rsults in no issuance of new tokens, no
1620This is something super.
1621
1622Jiri Jetmar | EOS Germany | jj@eosgermany.one
1623jem
1624Account creation RAM costs solution We have a total solution for RAM allocation, which rsults in no issuance of new tokens, no
1625I 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.
1626
1627jem
1628mao EOSREAL
1629This is something super.
1630Kind 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.
1631Laim Lais joined group via invite link
1632Sharif 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 »
1633
1634Nathan Rempel | GenerEOS Sydney
1635jem
1636Kind of embarassing how easy the solution is. Since we have a snapshot of the chain just prior to resignation, applying it is a
1637I 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?
1638
1639jem
1640Nathan Rempel | GenerEOS Sydney
1641I 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
1642No
1643
1644Bohdan CryptoLions 🦁
1645Nathan Rempel | GenerEOS Sydney
1646Any other candidates to spin up this testnet if @BohdanCryptoLions isn't available?
1647I am here, need to sleep sometimes =)
1648
1649Nathan Rempel | GenerEOS Sydney
1650Bohdan CryptoLions 🦁
1651I am here, need to sleep sometimes =)
1652I feel ya brother
1653
1654Michael Yeates
1655Nathan Rempel | GenerEOS Sydney
1656I 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
1657the eos in the ram and ramfee accounts is the exact amount that was spent for  ram by eosio
1658
1659Sharif Bouktila - EOS Dublinadmin
1660Both solutions were fine with me,  please think about how we collectively make a decision and close this one out.
1661
1662Jiri Jetmar | EOS Germany | jj@eosgermany.one
1663Sharif Bouktila - EOS Dublin
1664Both solutions were fine with me, please think about how we collectively make a decision and close this one out.
1665+1
1666
1667David P - EOS42
1668jem
1669Account creation RAM costs solution We have a total solution for RAM allocation, which rsults in no issuance of new tokens, no
1670This 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.
1671
1672jem
1673It was 4 lines of script, total.
1674
1675Nathan Rempel | GenerEOS Sydney
1676I 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?
1677
1678David P - EOS42
1679Fine 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.
1680
1681jem
1682GB 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.
1683
1684Bohdan CryptoLions 🦁
1685Nathan Rempel | GenerEOS Sydney
1686I feel ya brother
1687is testnet still needed? what data use to deploy?
1688
1689Sharif Bouktila - EOS Dublinadmin
1690David P - EOS42
1691This sounds much more elegant, how difficult is that to implement? As you’ll note from the global voting many BPs seem to just b
1692The question of which chain to launch is bigger.  
1693
1694It doesn't feel right that we are making it on what I believe is such a small issue. 
1695
1696How 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.
1697
1698Nathan Rempel | GenerEOS Sydney
1699Bohdan CryptoLions 🦁
1700is testnet still needed? what data use to deploy?
1701Would be nice if @bo_eossv and @dftle could provide an update, its been many hours
1702
1703jem
1704No one is arguing which chain to launch. It really doesn't matter.
1705
1706Michael Yeates
1707Sharif Bouktila - EOS Dublin
1708The 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
1709we should reach community consensus on these issues
1710
1711David P - EOS42
1712jem
1713GB made a snapshot of the chain after injection and immediately before resignation of eosio (done to create base for Acceptance
1714So 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.
1715
1716Sharif Bouktila - EOS Dublinadmin
1717jem
1718No one is arguing which chain to launch. It really doesn't matter.
1719Can your approach be applied to B-Chain also.
1720
1721David P - EOS42
1722Michael Yeates
1723we should reach community consensus on these issues
1724I’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.
1725
1726jem
1727Sharif Bouktila - EOS Dublin
1728Can your approach be applied to B-Chain also.
1729Yes, if they made the snapshot which had been promised to GB before it was launched.
1730
1731Sharif Bouktila - EOS Dublinadmin
1732David P - EOS42
1733I’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
1734Would you like to take it?
1735I agree
1736
1737Craig Murray - EOS BlockSmith
1738jem
1739Account creation RAM costs solution We have a total solution for RAM allocation, which rsults in no issuance of new tokens, no
1740Personally 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
1741
1742Sharif Bouktila - EOS Dublinadmin
1743jem
1744Yes, if they made the snapshot which had been promised to GB before it was launched.
1745So they would need a new one? Or is it possible on what they have now??   Sorry I need to get this 100% clear.
1746
1747Michael Yeates
1748they should be able to start a snapshot and fix it without rebooting
1749
1750David P - EOS42
1751Sharif Bouktila - EOS Dublin
1752Would you like to take it?
1753I 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
1754
1755jem
1756Sharif Bouktila - EOS Dublin
1757So they would need a new one? Or is it possible on what they have now?? Sorry I need to get this 100% clear.
1758I don't know. The snapshot had been promised, but was never delivered. I don't know if it was ever made.
1759
1760Joshua Qiu @EOSeco
1761jem
1762Yes, if they made the snapshot which had been promised to GB before it was launched.
1763can user sell initail ram?
1764
1765Sharif Bouktila - EOS Dublinadmin
1766David P - EOS42
1767I 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
1768I'll do this one then.   And ask for another Chair for the next one on the call.
1769
1770David P - EOS42
1771Craig Murray - EOS BlockSmith
1772Personally I think this issue was closed. I agree with Dan, we should just print tokens. We have a 72 hour old chain done this
1773Here’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?
1774
1775Craig Murray - EOS BlockSmith
1776David P - EOS42
1777Here’s the point - Dan was asked without any other solution proposed. If we now say it’s slightly messy solution that will requi
1778Dan already weighed in on this
1779
1780David P - EOS42
1781I think he’d probably say use the better solution if there’s no delay
1782
1783Craig Murray - EOS BlockSmith
1784there is delay
1785
1786David P - EOS42
1787Craig Murray - EOS BlockSmith
1788there is delay
1789What’s the delay?
1790
1791Craig Murray - EOS BlockSmith
1792restarting a chain, revalidating it, changing the boot sequence
1793
1794Joshua Qiu @EOSeco
1795i am thinking about sell inital ram, who should pay for this sell
1796
1797David P - EOS42
1798Sharif Bouktila - EOS Dublin
1799I'll do this one then. And ask for another Chair for the next one on the call.
1800Thanks, I also think you’re trying to be politically neutral here too
1801Craig Murray - EOS BlockSmith
1802restarting a chain, revalidating it, changing the boot sequence
1803Is that correct @jemxpat ?
1804
1805Zhao Yu@ EOSLaoMao.com
1806if user can sell ram, then the only thing fixed by jem’s new solution is the extra 2 or 3 EOS I think.
1807
1808Michael Yeates
1809they cannot sell their initial ram until someone else buys it
1810
1811Zhao Yu@ EOSLaoMao.com
1812so they can, as sell means there are buyers and sellers.
1813
1814Craig Murray - EOS BlockSmith
1815i cannot believe we're still debating this non-issue
1816
1817Michael Yeates
1818if they sell too much of their initial ram then their account will not function well
1819
1820Craig Murray - EOS BlockSmith
1821even Dan knows it's not a real issue
1822
1823Zhao Yu@ EOSLaoMao.com
1824Michael Yeates
1825if they sell too much of their initial ram then their account will not function well
1826what about I buy some more then sell it?
1827
1828jem
1829Maybe Dan "knows" it. But, it is wrong, and will look very bad to some.
1830
1831Craig Murray - EOS BlockSmith
1832jem
1833Maybe Dan "knows" it. But, it is wrong, and will look very bad to some.
1834glad you know more than Dan
1835you're not even a BP, what is your stake in all this, a non BP who speaks for an entire launch group?
1836
1837jem
1838I'm not a syncophant.
1839
1840Craig Murray - EOS BlockSmith
1841you think you know better than him though, clearly.
1842
1843jem
1844I think he is not omniscient.
1845
1846Craig Murray - EOS BlockSmith
1847no one does
1848
1849Zhao Yu@ EOSLaoMao.com
1850so 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
1851
1852Craig Murray - EOS BlockSmith
1853yes, 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
1854
1855Jiri Jetmar | EOS Germany | jj@eosgermany.one
1856if 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.
1857
1858jem
1859There is no extra 3 EOS in the chain which ran this. There was precisely 1000000000.0000 EOS.
1860
1861Zhao Yu@ EOSLaoMao.com
1862that I agree
1863
1864Michael Yeates
1865Jiri Jetmar | EOS Germany | jj@eosgermany.one
1866if we continue to deal with trivialities like this, then we see EOS trading at or below USD 5. That would destroy an enormous va
1867if we dont deal with these issues yet then we will have to face them on a live running chain
1868
1869Zhao Yu@ EOSLaoMao.com
1870Michael Yeates
1871if we dont deal with these issues yet then we will have to face them on a live running chain
1872so what kind of disasters we are talking about because of these 3 extra EOS?
1873
1874jem
1875It is curently 19k extra.
1876
1877Zhao Yu@ EOSLaoMao.com
1878no
1879user can sell ram
1880
1881Michael Yeates
1882Zhao Yu@ EOSLaoMao.com
1883so what kind of disasters we are talking about because of these 3 extra EOS?
1884public opinion backlash about the 20k tokens added
1885
1886Zhao Yu@ EOSLaoMao.com
1887ram is EOS too
1888Dr Ye EOS WashingtonDC - TChain
1889what is your most recent total block count that is increasing by the second?
1890
1891Jiri Jetmar | EOS Germany | jj@eosgermany.one
1892Michael Yeates
1893if we dont deal with these issues yet then we will have to face them on a live running chain
1894But this RAM issue is only an initial topic and the delta is very limited. I do not think that anybody cares..
1895
1896Zhao Yu@ EOSLaoMao.com
1897Michael Yeates
1898public opinion backlash about the 20k tokens added
1899there’s no 20K, there’s 3 EOS, user can sell ram, ram is EOS
1900
1901Michael Yeates
1902the supply discrepency is 20k
1903
1904Sandwich
1905General Information: Rounding a number after calculations, not before, can reduce accumulative dust.
1906
1907Zhao Yu@ EOSLaoMao.com
1908Michael Yeates
1909public opinion backlash about the 20k tokens added
1910we will tell public the truth. and the truth is, we give them some free ram. that’s all.
1911
1912Jiri Jetmar | EOS Germany | jj@eosgermany.one
1913Zhao Yu@ EOSLaoMao.com
1914we will tell public the truth. and the truth is, we give them some free ram. that’s all.
1915+1 .. every bank on the planet has delta in their books. It doesn't bother anyone, because it's negligible.
1916
1917Stuardo Rodríguez 🇬🇹
1918Just to confirm, do we have a call right now? Or in 12 hours?
1919
1920jem
1921One hour later.
1922
1923Stuardo Rodríguez 🇬🇹
1924In 1h thank you
1925
1926Sharif Bouktila - EOS Dublinadmin
1927GUYS - Lets keep it on topic and professional please!
1928Dr Ye EOS WashingtonDC - TChain
1929may i ask who can turn a node to produce blocks on boot-net?
1930
1931Stuardo Rodríguez 🇬🇹
1932I 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
1933Dr Ye EOS WashingtonDC - TChain
1934tons of things going on if you stay hands on
1935
1936Stuardo Rodríguez 🇬🇹
1937"net d" won't stall more than what we are already waiting
1938Dr Ye EOS WashingtonDC - TChain
1939anyone 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)
1940
1941Benjamin Wang | EOShenzhen
1942EOS is not a stock. The value of EOS is based on trust and consensus.
1943
1944Syed Jafri | EOS Cafe / Calgary
1945David P - EOS42
1946Here’s the point - Dan was asked without any other solution proposed. If we now say it’s slightly messy solution that will requi
1947I have a feeling Dan just wants the chain up before the hackathon :wink:
1948
1949Kyunghwan Kim - EOSeoul.io
1950I 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.
1951
1952https://gist.github.com/redjade/bdbcb10708e165b29d0301c5defa1d83
1953on_ramcost.md
1954[Photo]
1955
1956Thomas "Disclaimer" Cox (all opinions mine)
1957David P - EOS42
1958I’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
1959Longer term, a rotating chair is probably wise.
1960Dr Ye EOS WashingtonDC - TChain
1961Kyunghwan Kim - EOSeoul.io
1962I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
1963:+1:
1964
1965Nathan Rempel | GenerEOS Sydney
1966David P - EOS42
1967I’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
1968Can we try to follow a similar format, whoever curates the meeting. It seemed to be highly effective
1969
1970Thomas "Disclaimer" Cox (all opinions mine)
1971An agenda helps
1972What is the status of data entry of test cases and test results?
1973
1974David P - EOS42
1975Syed Jafri | EOS Cafe / Calgary
1976I have a feeling Dan just wants the chain up before the hackathon :wink:
1977:grin: I think you’re right! See you in SF soon? I arrived last night.
1978Thomas "Disclaimer" Cox (all opinions mine)
1979An agenda helps
1980@sharifbouktila want a hand with some thoughts on that? I’ll DM
1981Let’s just keep the call positive and productive all, we all want the same thing
1982
1983Craig Murray - EOS BlockSmith
1984I'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
1985
1986Jiri Jetmar | EOS Germany | jj@eosgermany.one
1987David P - EOS42
1988Let’s just keep the call positive and productive all, we all want the same thing
1989100% agree!
1990
1991Syed Jafri | EOS Cafe / Calgary
1992David P - EOS42
1993:grin: I think you’re right! See you in SF soon? I arrived last night.
1994About to hop in a plane in 20 :grin:
1995
1996David P - EOS42
1997Craig Murray - EOS BlockSmith
1998I'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
1999Understand, no doubt as a senior technologist we need you focused on the launch so if it’s ongoing you can’t really do both.
2000Syed Jafri | EOS Cafe / Calgary
2001About to hop in a plane in 20 :grin:
2002Great, 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
2003
2004Craig Murray - EOS BlockSmith
2005David P - EOS42
2006Understand, no doubt as a senior technologist we need you focused on the launch so if it’s ongoing you can’t really do both.
2007Jerry 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
2008
2009Nathan Rempel | GenerEOS Sydney
2010I'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
2011
2012Craig Murray - EOS BlockSmith
2013a full 3rd party security audit takes a lot of time.  YOu can't do that in a day, it takes weeks to test properly
2014
2015David P - EOS42
2016Craig Murray - EOS BlockSmith
2017Jerry is a far better systems admin than I am. Likely he can handle anything that comes up. I'm just concerned right now becau
2018Come 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
2019Nathan Rempel | GenerEOS Sydney
2020I'm also concerned we haven't heard from our friends in China on a joint testnet to run against and have these audits performed
2021@maoyifeng @bo_eossv Are either of you able to help get an update on this?
2022
2023Nathan Rempel | GenerEOS Sydney
2024Craig Murray - EOS BlockSmith
2025a full 3rd party security audit takes a lot of time. YOu can't do that in a day, it takes weeks to test properly
2026Yes, 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
2027
2028Sharif Bouktila - EOS Dublinadmin
2029https://zoom.us/j/786777697
2030
2031Zoom Video
2032Join our Cloud HD Video Meeting now
2033Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
2034Call in 7 minutes
2035
2036mao EOSREAL
2037David P - EOS42
2038@maoyifeng @bo_eossv Are either of you able to help get an update on this?
2039I am still on plane.  Can not join this call. Please update me your progress.
2040Hyunwoong JI - EOSeoul.io
2041Kyunghwan Kim - EOSeoul.io
2042I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
2043:+1:
2044
2045Nathan Rempel | GenerEOS Sydney
2046@sharifbouktila on Jungle I *just* tested using my genesis account to successfully create and regproducer successfully
2047using 8kb ram, 1EOS/1EOS cpu/net
2048
2049Brett Jeffery @ EOS the World
2050Morning meeting starting
2051https://zoom.us/j/786777697
2052
2053Zoom Video
2054Join our Cloud HD Video Meeting now
2055Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
2056- eoseoul.io DS Lim
2057Kyunghwan Kim - EOSeoul.io
2058I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
2059:+1::+1:
2060
2061jem
2062Kyunghwan Kim - EOSeoul.io
2063I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
2064Excellent! :+1:
2065
2066Yongkil Kwon - EOSeoul.io
2067Kyunghwan Kim - EOSeoul.io
2068I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
2069Awesome! :+1:
2070Dr Ye EOS WashingtonDC - TChain
2071with 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?
2072
2073David Moss
2074Yes, and there should be more than one.
2075
2076Nathan Rempel | GenerEOS Sydney
2077mainnet in production that's not a mainnet? need to clarify the semantics there
2078Dr Ye EOS WashingtonDC - TChain
2079the boot-net for now
2080
2081Nathan Rempel | GenerEOS Sydney
2082anyone can already do this... it's just a public test net
2083and should be
2084
2085Craig Murray - EOS BlockSmith
2086cryptolions has been doing this for a month or more
2087they are currently running latest tag
2088Dr Ye EOS WashingtonDC - TChain
2089yeah... not with real money though
2090
2091Craig Murray - EOS BlockSmith
2092you cannot run with real money and not be the mainnet
2093
2094David Moss
2095Faucets
2096
2097Craig Murray - EOS BlockSmith
2098once 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"
2099
2100David Moss
2101Or sys
2102
2103Craig Murray - EOS BlockSmith
2104yes cryptolions has faucets
2105Dr Ye EOS WashingtonDC - TChain
2106we are testing on jungle with faucets
2107Dr Ye EOS WashingtonDC - TChain invited Terry Hsiao and 3 more
2108
2109Nathan Rempel | GenerEOS Sydney
2110Very productive call, thanks everyone. I'll look forward to seeing testing results appearing in the spreadsheet, lets not lose sight of that :)
2111Perhaps we can add this document to the pin to keep eyes on it: https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit?usp=sharing
2112
2113Google Docs
2114EOS UAT - User Acceptance Testing
2115Home
2116
2117
2118Create a Case, Record a Test
2119Procedure 1: Create a Case
2120STEPS
21211, Confirm your case does not yet exist
2122a, Click the red Cases tab at the bo...
2123
2124Craig Murray - EOS BlockSmith
2125that felt like a very productive meeting
2126
2127David P - EOS42
2128So 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
2129Could somebody confirm who on this channel represents them or 'EOSBschool', it seems they are not a Block Producer from an intial look
2130Craig Murray - EOS BlockSmith
2131that felt like a very productive meeting
2132Yes, we need to all stay focused on the issues at hand and productive resolution now.
2133Benjamin Wang | EOShenzhen invited delin he
2134
2135Kyunghwan Kim - EOSeoul.io
2136Kyunghwan Kim - EOSeoul.io
2137I wrote some notes for documenting and understanding what is going on current ram cost approaches and its consequences technical
2138And 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.
2139
2140I'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++.
2141
2142Sharif Bouktila - EOS Dublinadmin
2143Does anyone know who in here is from the account who live-streamed that call?
2144Else I’ll start removing people who haven’t been active in the past 48 hours in this channel and lock it
2145
2146Mathieu Boulianne - EOS Canada
2147Sharif Bouktila - EOS Dublin
2148Does anyone know who in here is from the account who live-streamed that call?
2149The Zoom link was shared in other public channels
2150
2151Hubert Chang-EOSeoul.io
2152All I heard was someone saying 'EOSBS'? But maybe  it is best to contact  Mark.
2153
2154David P - EOS42
2155Hubert Chang-EOSeoul.io
2156All I heard was someone saying 'EOSBS'? But maybe it is best to contact Mark.
2157EOSBSchool - Malcolm Silberman
2158
2159Sharif Bouktila - EOS Dublinadmin
2160Mathieu Boulianne - EOS Canada
2161The Zoom link was shared in other public channels
2162Crazy 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
2163
2164David P - EOS42
2165I don't know who they are on here
2166They probably are on here
2167
2168Josh Kauffman - EOS Canada
2169If 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.
2170
2171Sharif Bouktila - EOS Dublinadmin
2172There was 140 today at one point
2173
2174David P - EOS42
2175[Photo]
2176This guy
2177
2178Hubert Chang-EOSeoul.io
2179Maybe our friends in US can help us out.
2180Kevin? :) He seems to know just about everyone
2181
2182Sharif Bouktila - EOS Dublinadmin
2183I don’t think they are private , but hate the idea of someone recording and streaming without consent. 
2184
2185Our position and decisions are market sensitive.
2186
2187Brett Jeffery @ EOS the World
2188Sharif Bouktila - EOS Dublin
2189Else I’ll start removing people who haven’t been active in the past 48 hours in this channel and lock it
2190Understood. 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:
2191
2192David P - EOS42
2193Sharif Bouktila - EOS Dublin
2194I don’t think they are private , but hate the idea of someone recording and streaming without consent. Our position and decisi
2195It'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.
2196
2197Sukesh Tedla (EOSGreen)
2198Brett Jeffery @ EOS the World
2199Understood. 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:
2200+1
2201
2202David P - EOS42
2203Anyway let's get back to onto more important matters
2204
2205Sukesh Tedla (EOSGreen)
2206David P - EOS42
2207Anyway let's get back to onto more important matters
2208:+1:
2209
2210Sharif Bouktila - EOS Dublinadmin
2211Brett Jeffery @ EOS the World
2212Understood. 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:
2213That’s fine , I don’t have the answer just yet.  
2214
2215Reminds me of my post months ago about our mantra of DBAA - “Don’t be an a**hole”
2216
2217Ville Sundell
2218So, is the consensus now, that the new selected ABP will launch their own chain?
2219
2220David P - EOS42
2221Sharif Bouktila - EOS Dublin
2222That’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
2223Somebody pin this from Sharif.. sometimes the world needs to hear the sweet tones of an Irishman telling you that
2224
2225Brett Jeffery @ EOS the World
2226not criticizing you, just don’t want to get our team locked out just because we’re not posting much.
2227
2228Sharif Bouktila - EOS Dublinadmin
2229Very good call other than that , well done all!!
2230
2231Craig Murray - EOS BlockSmith
2232Ville Sundell
2233So, is the consensus now, that the new selected ABP will launch their own chain?
2234no
2235
2236Ville Sundell
2237Craig Murray - EOS BlockSmith
2238no
2239Good :laughing: (Personal opinion only, I think the existing chain is good to take over by the appointed ABP)
2240
2241Marc-Antoine Ross - EOS Canadaadmin
2242All, 
2243
2244Thanks for another productive call!
2245
2246PRIORITY: get that testing done! https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ
2247
2248Find bellow the minutes, if you find anything not accurate, please suggest/comment and we will fix.
2249The raw log is included at the bottom of the document.
2250
2251https://docs.google.com/document/d/17cwUuPoaH1NAYfSGgvomSvjTkDrMHdVhLaxCS5t-orQ
2252
2253Next steps:
2254June 7, 0100 UTC: the next go/no go discussion, hopefully with the initial security report in hand
2255    Meshing and ABP protection
2256    Ben from shEOS asks: How can we insure that voting portals are handling private keys well?
2257    More?
2258
2259
2260Thanks, good after-mor-night!
2261
2262Google Docs
2263EOS UAT - User Acceptance Testing
2264Home
2265
2266
2267Create a Case, Record a Test
2268Procedure 1: Create a Case
2269STEPS
22701, Confirm your case does not yet exist
2271a, Click the red Cases tab at the bo...
2272Marc-Antoine Ross - EOS Canada pinned « All, Thanks for another productive call! PRIORITY: get that testing done! https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2»
2273
2274Denis | EOS Nation
2275Syed Jafri | EOS Cafe / Calgary
2276Cypherglass offered to do a video
2277:+1: thanks Cypherglass, your last video was very professional and your messaging was accurate to the current events.
2278Kevin Rose - EOS New York
2279https://steemit.com/eos/@eosnewyork/the-eos-mainnet-launch-security-and-software-testing
2280Amazing :muscle::muscle: we should continue to use the same lingo P0 & P1 when presenting the security audits findings
2281Syed Jafri | EOS Cafe / Calgary
2282I think Bohdan has one of the most experience in the community for launching testnets. He is also a relatively neutral party tha
2283:+1: agreed, Jungle has the most experience in launching new Testnets
2284Craig Murray - EOS BlockSmith
2285nice job staying away from calling out these launch cohorts by name. Well done sir, thanks
2286+1 we should not be putting any labels anymore, we're all in this together
2287Bo - EOS Silicon Valley
2288We 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
2289:muscle: we fully support your efforts! Everyone is very happy you and the other Chinese BPC'S/Community/Exchanges are pushing for this.
2290
2291Looking forward to see these findings (good or bad) We will be more informed on our next steps moving forward after these results surface.
2292
2293David P - EOS42
2294I 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.
2295
2296Sharif Bouktila - EOS Dublinadmin
2297David P - EOS42
2298I 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
2299+1
2300
2301Mr.Z
2302David P - EOS42
2303I 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
2304Can't agree more!
2305
2306Ben Sigman
2307David P - EOS42
2308I 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
2309What will we call it?
2310
2311Kevin Rose - EOS New York
2312First few digits of the chain ID seems to make sense.
2313
2314Craig Murray - EOS BlockSmith
2315unfortuantely the chain starting in 0d6c has been forked a few times, so it's hard to refer to it just by chain id
2316there 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.
2317
2318Sharif Bouktila - EOS Dublinadmin
2319A-Z , hopefully we don’t need > 26
2320
2321David P - EOS42
2322Ben Sigman
2323What will we call it?
2324Anything 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.
2325
2326Sharif Bouktila - EOS Dublinadmin
2327Or how about jungle animals - a nod to the super work done there
2328
2329Craig Murray - EOS BlockSmith
2330so 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?
2331where C D and E have the same chain ID
2332
2333Sharif Bouktila - EOS Dublinadmin
2334Whatever works
2335
2336Michael Yeates
2337there are no multiple forks
2338we have the one chain and separate private chains for testing
2339out blocks db is available for download and testing
2340
2341Craig Murray - EOS BlockSmith
2342those are forks because they have the same ID
2343that's the definition of a fork
2344it's not derogatory, it's jsut fact
2345i 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
2346we're talking about a way to describe them that doesn't use these silly team names
2347trying to say they are not forks is just confusing to people... they see the chain ID and think they are on the right one
2348
2349Denis | EOS Nation
2350Marc-Antoine Ross - EOS Canada
2351All, Thanks for the productive call. Find below the minutes, if you find anything not accurate, please suggest/comment and w
2352:+1::+1: Marc is the best scribe ever!
2353
2354Patrick B - Aloha EOS
2355Denis | EOS Nation
2356:+1::+1: Marc is the best scribe ever!
2357career change? :D
2358
2359Denis | EOS Nation
2360Jose Toriello
2361I suggest "issuing" and not "printing" as a better vocabulary, especially given the sensitivity around the subject.
2362Agreed, I think the wording "print vs. issue" for optics the word "issuing" should be used for the global message.
2363
2364CC: Cypherglass & EOS New York
2365Patrick B - Aloha EOS
2366career change? :D
2367:joy: full-time scribe :scroll:
2368
2369Patrick B - Aloha EOS
2370haha
2371
2372Jose Toriello
2373Craig Murray - EOS BlockSmith
2374we're talking about a way to describe them that doesn't use these silly team names
2375+1
2376
2377Denis | EOS Nation
2378Timothy Lewis
2379There has been a potential well written solution to the whole problem that was painstakingly written by @resvera ... Has it been
2380:-1: disagree, attempting to reimplement anything that touches token balances would jeopardize the entire validation process (this is why I mentioned +2 days)
2381
2382If we change anything that's related to the token balance, then we're back at step 0 with zero confidence on that new chain.
2383
2384This type of change would cause a drastic delay (for what reason?)
2385
2386Craig Murray - EOS BlockSmith
2387and woudl also degrate public trust that we are making progress
2388
2389Denis | EOS Nation
2390David Moss
2391I agree it's a good solution. Would it require restarting the mainnet candidate>?
2392🤔 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.
2393
2394David P - EOS42
2395Timothy Lewis
2396There has been a potential well written solution to the whole problem that was painstakingly written by @resvera ... Has it been
2397If 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.
2398Alex - EOS SOCAL invited Cesar Diaz EOSoCal
2399
2400David P - EOS42
2401And 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.
2402
2403Craig Murray - EOS BlockSmith
2404Denis | EOS Nation
2405🤔 restarting a chain for the sake of testing new code that's untested would be a disaster. I personally would not have confiden
2406we'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
2407
2408Denis | EOS Nation
2409David P - EOS42
2410If 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
2411If we spin up a new chain we're at day 0 again.
2412
2413The advantage of chain 579a is the timestamp, if our timestamp changes for today that means we've only tested this chain for <24 hours
2414
2415deck - EOS New York
2416Denis | EOS Nation
2417If 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
2418What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
2419
2420Timothy Lewis
2421deck - EOS New York
2422What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
2423+1
2424
2425Denis | EOS Nation
2426{"initial_timestamp":"2018-06-03T13:04:31","initial_key":"EOS7m4uBgRXBM5DbXFX7FTrNiZyRzxfktmto6qQTzc2z3BhgAGHKM"}
2427
2428June 3rd is the timestamp of 579a
2429
2430Timothy Lewis
2431Why does that matter
2432
2433Craig Murray - EOS BlockSmith
2434deck - EOS New York
2435What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
2436it 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
2437
2438Denis | EOS Nation
2439The software isn't changing unless we find P0 or P1
2440
2441Timothy Lewis
2442Why? I’d rather a chain that is correct.
2443“These guys can’t even get token issuance right, lol”
2444
2445Craig Murray - EOS BlockSmith
2446we're back to ram again?  ugh
2447
2448Denis | EOS Nation
2449deck - EOS New York
2450What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
2451:-1: more then running a few scripts.
2452
2453Starting a new chain for the sake of it says "we have no confidence in the chain we've booted and validated"
2454
2455David P - EOS42
2456deck - EOS New York
2457What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
2458Exactly.  Buddy is right I don't know why you think this takes long Denis, it doesn't.
2459
2460Denis | EOS Nation
2461Timothy Lewis
2462“These guys can’t even get token issuance right, lol”
2463:-1: so you're against BM's decision and the majority of the BPs?
2464
2465Timothy Lewis
2466Craig Murray - EOS BlockSmith
2467we're back to ram again? ugh
2468I’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.
2469
2470Denis | EOS Nation
2471Timothy Lewis
2472I’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
2473It's not a solution
2474
2475Craig Murray - EOS BlockSmith
2476what chain uses this solution?  Is this solution coded in github?  Tested?
2477
2478Timothy Lewis
2479Look above at the original post.
2480
2481Craig Murray - EOS BlockSmith
2482what are the p2p addresses so i can sync to this new "proper" chain?
2483
2484Timothy Lewis
2485Have a good day guys, I’m back to work.
2486
2487Jae Chung - HKEOS
2488Craig Murray - EOS BlockSmith
2489those are forks because they have the same ID
2490How else would you run an acceptance testing chain without forking?
2491just wondering
2492
2493David P - EOS42
2494Denis | EOS Nation
2495:-1: so you're against BM's decision and the majority of the BPs?
2496To 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.
2497
2498Craig Murray - EOS BlockSmith
2499David P - EOS42
2500Exactly. Buddy is right I don't know why you think this takes long Denis, it doesn't.
2501it 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
2502
2503Denis | EOS Nation
2504David P - EOS42
2505Exactly. Buddy is right I don't know why you think this takes long Denis, it doesn't.
2506Starting a new chain for the sake of it is not a good decision.
2507
2508If you don't agree with the RAM purchase, then join another chain that has a different chain injection process.
2509
2510Right now 579a has been validated and nothing is wrong with it
2511
2512David P - EOS42
2513Fair enough guys, I'm just trying to give everybody a chance here and keep us moving forwards.
2514
2515Craig Murray - EOS BlockSmith
2516a new chain is moving backwards unless we find a p0 or p1, we should not start a new chain
2517
2518Denis | EOS Nation
2519Craig Murray - EOS BlockSmith
2520it does actually. One person can run validation in 20 minutes but we have to provide time for BPs all over the world to validat
2521:+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
2522David P - EOS42
2523Fair enough guys, I'm just trying to give everybody a chance here and keep us moving forwards.
2524We are moving forward, wait for security audits from the Chinese community.
2525
2526If no P0 / P1 problems arise, we decide after all reading the findings and call a Go/NoGo meeting (whenever that day comes)
2527Craig Murray - EOS BlockSmith
2528a new chain is moving backwards unless we find a p0 or p1, we should not start a new chain
2529:ok_hand:
2530Jae Chung - HKEOS
2531How else would you run an acceptance testing chain without forking?
2532This just indicates that that Chain C is a "testnet" and not a "candidate chain"
2533
2534We've only got 1 real candidate chain by your comment
2535
2536Craig Murray - EOS BlockSmith
2537Jae Chung - HKEOS
2538How else would you run an acceptance testing chain without forking?
2539I did not suggest you would
2540
2541Jae Chung - HKEOS
2542Denis | EOS Nation
2543This just indicates that that Chain C is a "testnet" and not a "candidate chain" We've only got 1 real candidate chain by your
2544I 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.
2545
2546Craig Murray - EOS BlockSmith
2547i 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
2548
2549Michael Yeates
2550the 1178 chain is in the hands of the community
2551
2552Jae Chung - HKEOS
2553Michael Yeates
2554out blocks db is available for download and testing
2555^
2556
2557Michael Yeates
2558paused and distributed
2559
2560Jae Chung - HKEOS
2561we have a public endpoint that we stopped with the fully synced copy at 11778
2562
2563Craig Murray - EOS BlockSmith
2564who is running the boot node for it?
2565
2566Thomas "Disclaimer" Cox (all opinions mine)
2567David Moss
2568Faucets
2569Real public keys from the snapshot? Or a blank testnet?
2570
2571Michael Yeates
2572Craig Murray - EOS BlockSmith
2573who is running the boot node for it?
2574its anonymous
2575we may have just found something
2576
2577Craig Murray - EOS BlockSmith
2578what are the public endpoints for this paused chain?
2579Peter Bue | EOSAmericas invited James Davis
2580
2581Jae Chung - HKEOS
2582Craig Murray - EOS BlockSmith
2583what are the public endpoints for this paused chain?
2584Craig, 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?
2585Here's a block database you can sync from, for your convenience: https://transfer.sh/OIyZl/boot-mainnet-post-resign-ramfix.tar.gz
2586
2587Craig Murray - EOS BlockSmith
2588as I said I'm having trouble with your endpoints today but if you dont want to hel that's fine
2589dont help
2590
2591Jae Chung - HKEOS
2592"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.
2593
2594Sharif Bouktila - EOS Dublinadmin
2595Guys looks like @jaechung was helping,  there is plenty of other channels to discuss endpoints etc..
2596Lets try and keep in here on point.   We can spin up another channel for Which Chain type discussions. 
2597
2598If I'm off topic,  I'd expect someone to nudge me back into line, so please don't take offence.
2599
2600Craig Murray - EOS BlockSmith
2601Sharif Bouktila - EOS Dublin
2602Lets 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
2603:+1:
2604
2605Denis | EOS Nation
2606Sharif Bouktila - EOS Dublin
2607Lets 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
2608:+1:agreed, we should keep the discussions on topic.
2609
2610Peter Bue | EOSAmericas
2611Sharif Bouktila - EOS Dublin
2612Lets 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
2613:+1::+1:
2614
2615Hugo Yang - EOS Silicon Valley
2616Tactical 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?
2617
2618Denis | EOS Nation
2619Hugo Yang - EOS Silicon Valley
2620Tactical Question for 579a chain: if we decide to promote it as the chain voters / BPCs go, how do we deal with all those “dummy
2621That could be a discussion topic for tonight (I won't be able to attend, in a plane during call)
2622
2623IMO: 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.
2624
2625The filesize of these blocks is minimal, including them isn't a big deal for "launching"
2626
2627My vote: Keep empty blocks until we launch
2628
2629Ben Sigman
2630Denis | EOS Nation
2631That 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
2632So 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?
2633
2634Timothy Lewis
2635Updated: https://gist.github.com/redjade/bdbcb10708e165b29d0301c5defa1d83
2636on_ramcost.md
2637[Photo]
2638
2639Sharif Bouktila - EOS Dublinadmin
2640Folks 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 ) 
2641
2642If I removed someone from your team,  feel free to contact me directly.   
2643
2644@marcantoineross and @xebb82 are also admins , and people in here should be able to invite others.
2645
2646deck - EOS New York
2647Sharif Bouktila - EOS Dublin
2648Folks 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
2649Thanks. Do we also want to be careful with who we share the zoom links?
2650
2651Sharif Bouktila - EOS Dublinadmin
2652If 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.  
2653
2654Can obv put passwords but posting here is kind of the same thing. 
2655
2656I think the message sent out was probably clear enough that until we have a consensus we don't want calls streamed.
2657
2658Rob Finch - Cypherglass.com (Block Producer)
2659Syed Jafri | EOS Cafe / Calgary
2660Cypherglass offered to do a video
2661Happy to do a video. Please send me any details you’d like conveyed.
2662
2663Thomas "Disclaimer" Cox (all opinions mine)
2664I 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
2665
2666Sharif Bouktila - EOS Dublinadmin
2667Thomas "Disclaimer" Cox (all opinions mine)
2668I had random tourists watching several of my breakout calls the last few days. I gave them three chances to rename themselves wi
2669Sounds like a good approach.
2670
2671Kyle - EOSVibes
2672Rob Finch - Cypherglass.com (Block Producer)
2673Happy to do a video. Please send me any details you’d like conveyed.
2674I'm also happy to do a video. Although I think this should be Steemed as an EMLG too.
2675
2676Sharif Bouktila - EOS Dublinadmin
2677The 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.   
2678
2679Personally I don't think I could watch it back,  but I know there is lots of interest.
2680
2681Kyle - EOSVibes
2682Sharif Bouktila - EOS Dublin
2683The Videos are being recorded and I think should either be released or edited (to remove noise, bad audio etc.. ) and released a
2684I 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!!!
2685
2686Sharif Bouktila - EOS Dublinadmin
2687I hear you!  - EOS FIREHOSE 
2688
2689Personally I don't think the RAM question worth going out with for now.   But others might have a different opinion.
2690
2691Jose Toriello
2692Kyle - EOSVibes
2693I meant a video regarding the eosio issuance of tokens to gift the genesis accounts with free ram - that's what was being raised
2694Yup
2695Sharif Bouktila - EOS Dublin
2696I hear you! - EOS FIREHOSE Personally I don't think the RAM question worth going out with for now. But others might have a
2697Agree. Not worth it. It will only heighten the controversy.
2698
2699David Moss
2700@igorls you here?
2701
2702Igor Lins e Silva - EOS Rio
2703yes
2704
2705Sharif Bouktila - EOS Dublinadmin
2706@DavidMoss
2707
2708Ben Sigman
2709I just popped up this site
2710https://status.producer.vote/
2711
2712EOS Mainnet Status
2713This site shows the daily report from the EOS launch.
2714
2715Sharif Bouktila - EOS Dublinadmin
2716Ben Sigman
2717I just popped up this site
2718You should work in IT ,  nice work!
2719
2720Sukesh Tedla (EOSGreen)
2721Ben Sigman
2722https://status.producer.vote/
2723This is cool. Thanks for your effort.
2724
2725Sharif Bouktila - EOS Dublinadmin
2726Ben Sigman
2727https://status.producer.vote/
2728Hopefully it will be obsolete soon , although would be a nice place for BPs to push performance stats etc...
2729
2730Peter Sveda EOS Germany
2731Sharif Bouktila - EOS Dublin
2732Hopefully it will be obsolete soon , although would be a nice place for BPs to push performance stats etc...
2733:+1:
2734
2735Kyle - EOSVibes
2736Ben Sigman
2737https://status.producer.vote/
2738Helpful. Thanks Ben :+1:
2739Peter Bue | EOSAmericas invited Douglas Horn | EOSAmericas
2740
2741Rob Finch - Cypherglass.com (Block Producer)
2742Kyle - EOSVibes
2743I meant a video regarding the eosio issuance of tokens to gift the genesis accounts with free ram - that's what was being raised
2744The most important thing to convey is that the tokens are basically burned because they’re locked in the system account forever. 
2745
2746If people know that the 12k tokens are a *necessary* step in launching the chain, they will be fine with the decision.
2747
2748Kyle - EOSVibes
2749Rob Finch - Cypherglass.com (Block Producer)
2750The most important thing to convey is that the tokens are basically burned because they’re locked in the system account forever.
2751Then is it even worth conveying?
2752
2753Timothy Lewis
2754But they aren't being burned.
2755So that's not correct information.
2756
2757Sam - EOS Dublin
2758Ben Sigman
2759I just popped up this site
2760Looks 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
2761
2762Rob Finch - Cypherglass.com (Block Producer)
2763Kyle - EOSVibes
2764Then is it even worth conveying?
2765Probably not.
2766
2767Timothy Lewis
2768Kyle - EOSVibes
2769I meant a video regarding the eosio issuance of tokens to gift the genesis accounts with free ram - that's what was being raised
2770I 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?"
2771
2772mini - EOS Argentina
2773Timothy Lewis
2774I think the issue being raised is that the initial supply will be wrong. "If they can't even get the initial supply right, what
2775We didn't reach consensus on this yesterday?
2776
2777Timothy Lewis
2778That's becuase there was no fix.
2779We are testing a fix. If it fixes, it will be brought up. If it doesn't we are comfortable launching incorrect.
2780
2781Kyle - EOSVibes
278212k are being locked in the System contract forever though right? & There is no way for these EOS to ever be released right?
2783
2784Timothy Lewis
2785it's actually more like 2.0xxxx that will be moved to an unavailable account. It will affect initial RAM costs and BP rewards slightly.
2786It's not a "critical" system issue by any means.
2787It is an optical issue, in my opinion.
2788
2789Sharif Bouktila - EOS Dublinadmin
2790Why not manually add inflation (4%) for Worker Proposals from when the chain was created.  And use that to pay for Ram? 
2791
2792Put the rest into the WP fund.   (We are going to need it)
2793I'm also fine with the create & burn option to be clear.
2794
2795Kyle - EOSVibes
2796I'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).
2797Yep, send them to a null account when done.
2798
2799Timothy Lewis
2800Kyle - EOSVibes
2801I'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
2802That was never on the table.
2803Currently 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... )
2804Actually... Why don't you all just charge one of my accounts and we create a WP to repay me.
2805It's like 20k tokens, right?
2806
2807Sharif Bouktila - EOS Dublinadmin
2808Don't like that , but thanks for the offer.   - Please vote for us 🙂
2809
2810Timothy Lewis
2811I'll do anon
2812
2813Sharif Bouktila - EOS Dublinadmin
2814We'll never get a WP approved for a repay.  We don't even have a Worker Proposal process designed yet.
2815Why not manually add inflation (4%) for Worker Proposals from when the chain was created.  And use that to pay for Ram?
2816Its like 100k per day
2817
2818Kyle - EOSVibes
2819Why 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.
2820
2821Timothy Lewis
2822Sharif Bouktila - EOS Dublin
2823Why not manually add inflation (4%) for Worker Proposals from when the chain was created. And use that to pay for Ram?
2824I like this.
2825maybe.
2826let me think.
2827
2828Kyle - EOSVibes
2829Whatever 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.
2830
2831Timothy Lewis
2832Kyle - EOSVibes
2833Whatever the decision, we should communally Steemit as an EMLG post, maybe along with other info/updates at the time. We can vid
2834+1
2835And 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.
2836
2837Sharif Bouktila - EOS Dublinadmin
2838Kyle - EOSVibes
2839Whatever the decision, we should communally Steemit as an EMLG post, maybe along with other info/updates at the time. We can vid
2840+1
2841I think we are over thinking this one.  
2842
2843Its not material , lost in the roundings after a couple of days of the chain running.
2844
2845Kyle - EOSVibes
2846@trustlayer Yes
2847Sharif Bouktila - EOS Dublin
2848I think we are over thinking this one. Its not material , lost in the roundings after a couple of days of the chain running.
2849& Yes
2850
2851Kevin Rose - EOS New York
2852Kyle - EOSVibes
2853Whatever the decision, we should communally Steemit as an EMLG post, maybe along with other info/updates at the time. We can vid
2854Agree. Not against @finchify making a video, he’s very good at it. But we need a “faceless” statement as well.
2855
2856Timothy Lewis
2857With a mask and a voice distorter.
2858
2859Sharif Bouktila - EOS Dublinadmin
2860I don't think anyone should make a video until an agreed period after official statements.
2861
2862Timothy Lewis
2863Sharif Bouktila - EOS Dublin
2864I don't think anyone should make a video until an agreed period after official statements.
2865+1
2866
2867Kevin Rose - EOS New York
2868Timothy Lewis
2869With a mask and a voice distorter.
2870I can do a mean Darth Vader.
2871
2872Kyle - EOSVibes
2873Sharif Bouktila - EOS Dublin
2874I don't think anyone should make a video until an agreed period after official statements.
2875+1
2876Current 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.
2877This 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!
2878I really hope it stays like this...
2879
2880Sharif Bouktila - EOS Dublinadmin
2881Really is a solid group of people, I'm more and more optimistic each day.
2882But lets stay on topic ... How is the test plans coming along 🙂
2883
2884Ben Sigman
2885Sam - EOS Dublin
2886Looks 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
2887Yes I can change it up
2888
2889Shaheen Counts - EOS BlockSmith
2890Kevin Rose - EOS New York
2891I can do a mean Darth Vader.
2892I’d like to see this.
2893
2894Kevin Rose - EOS New York
2895Shaheen Counts - EOS BlockSmith
2896I’d like to see this.
2897I'm better at Golem from LOTR. #tulip
2898
2899Sam - EOS Dublin
2900Ben Sigman
2901Yes I can change it up
2902Thanks, the countdown is really helpful as time is just a blur right now 🙂
2903
2904Shaheen Counts - EOS BlockSmith
2905Kevin Rose - EOS New York
2906I'm better at Golem from LOTR. #tulip
2907I do a mean golem myself.   We
2908Might have to have a golem- off at Tulip.
2909
2910Ben Sigman
2911Shaheen Counts - EOS BlockSmith
2912I’d like to see this.
2913Proof of Vader requested by 0100
2914Sam - EOS Dublin
2915Thanks, the countdown is really helpful as time is just a blur right now 🙂
2916Well, I believe that there will be a call tonight
2917But not to vote
2918
2919Branden Espinoza
2920I can do Chewbacca.
2921
2922Timothy Lewis
2923Branden Espinoza
2924I can do Chewbacca.
2925That would be hilarious.
2926With the electronic mask.
2927You'd be perfect for it.
2928(the msg)
2929
2930Shaheen Counts - EOS BlockSmith
2931Branden Espinoza
2932I can do Chewbacca.
2933Haha
2934
2935Branden Espinoza
2936Timothy Lewis
2937(the msg)
2938Oh geeze.
2939I am happy to help however I can. :grin:
2940
2941Kevin Rose - EOS New York
2942Shaheen Counts - EOS BlockSmith
2943I do a mean golem myself. We Might have to have a golem- off at Tulip.
2944I’ll take “Things No One Wants” for $1,000, Alex.
2945
2946Shaheen Counts - EOS BlockSmith
2947Hahaha
2948
2949Sharif Bouktila - EOS Dublinadmin
2950Kevin Rose - EOS New York
2951I’ll take “Things No One Wants” for $1,000, Alex.
2952Thank you @eosnewyork , see you on the other side
2953
2954David P - EOS42
2955Timothy Lewis
2956We are testing a fix. If it fixes, it will be brought up. If it doesn't we are comfortable launching incorrect.
2957Right approach :+1:
2958
2959Josh Kauffman - EOS Canada
2960Nice 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.
2961
2962Sharif Bouktila - EOS Dublinadmin
2963Josh Kauffman - EOS Canada
2964Nice 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
2965The natural endpoint of all this is a dance off.  
2966
2967I trust Kev and Blue Jays to be neutral in judging.
2968
2969Stuardo Rodríguez 🇬🇹
2970Craig Murray - EOS BlockSmith
2971a new chain is moving backwards unless we find a p0 or p1, we should not start a new chain
2972In 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?
2973
2974Roman CryptoLions
2975Sharif Bouktila - EOS Dublin
2976The natural endpoint of all this is a dance off. I trust Kev and Blue Jays to be neutral in judging.
2977zoom call coming up?
2978
2979Nathan Rempel | GenerEOS Sydney
2980in one hour i think
2981
2982Kevin Rose - EOS New York
2983Sharif Bouktila - EOS Dublin
2984The natural endpoint of all this is a dance off. I trust Kev and Blue Jays to be neutral in judging.
2985I should start stretching now then.
2986
2987Marc-Antoine Ross - EOS Canadaadmin
2988Roman CryptoLions
2989zoom call coming up?
2990In one hour yes
2991
2992Nathan Rempel | GenerEOS Sydney
2993I see that eos-mainnet is 80 commits behind eosio
2994
2995Sam - EOS Dublin
2996Roman CryptoLions
2997zoom call coming up?
2998@Bensig created a handy tracker for exactly that! https://status.producer.vote
2999
3000EOS Mainnet Status
3001This site shows the daily report from the EOS launch.
3002Marc-Antoine Ross - EOS Canada invited Celu - Blockgenic
3003Celu - Blockgenic invited Jk (Blockgenic)
3004
3005Peter Bue | EOSAmericas
3006^ I'd also like to confirm the call.
3007
3008Craig Murray - EOS BlockSmith
3009Nathan Rempel | GenerEOS Sydney
3010I see that eos-mainnet is 80 commits behind eosio
3011yes, but I'm not sure it needs to track master.  I suspect they will merge based on new tags and certainly new versioned releases
3012
3013Nathan Rempel | GenerEOS Sydney
3014Craig Murray - EOS BlockSmith
3015yes, but I'm not sure it needs to track master. I suspect they will merge based on new tags and certainly new versioned release
3016Fair enough
3017
3018Andrey Marchuk
3019and David confirmed on the morning call that there are no critical fixes to worry about
3020
3021Marc-Antoine Ross - EOS Canadaadmin
3022All,
3023
3024Here's the proposed agenda:
3025Security report update - Dafeng EOS Asia
3026ABP selection update - Kevin EOS New York
3027go / no go
3028Ben from shEOS asks: How can we insure that voting portals are handling private keys well?
3029    Create a sub-team to prepare recommendations?
3030
3031https://zoom.us/j/885770550
3032
3033Zoom Video
3034Join our Cloud HD Video Meeting now
3035Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
3036Marc-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 »
3037
3038Timothy Lewis
3039Marc-Antoine Ross - EOS Canada
3040All, Here's the proposed agenda: Security report update - Dafeng EOS Asia ABP selection update - Kevin EOS New York go / no go
3041Time?
3042
3043David Moss
30446pm
3045
3046Marc-Antoine Ross - EOS Canadaadmin
3047Now!
3048Timothy Lewis
3049Time?
3050It's always 0100UTC and 1300UTC until further notice
3051
3052Craig Murray - EOS BlockSmith
3053Marc-Antoine Ross - EOS Canada
3054It's always 0100UTC and 1300UTC until further notice
3055FOREVER!
3056
3057Timothy Lewis
3058🙂
3059
3060Bo - EOS Silicon Valley
3061 191 KB
3062 
3063James Sutherland - Cypherglass.com
3064 702 KB
3065 
3066Andrey Marchuk
3067thanks
3068
3069James Sutherland - Cypherglass.com
3070Google mangled it, but it's somewhat readable
3071
3072Nathan Rempel | GenerEOS Sydney
3073the github translates pretty well
3074
3075Devin Lee KOREOS.IO
3076James Sutherland - Cypherglass.com
3077English_Auto_Translation_超级节点安全审计方案初稿.pdf
3078Already reported by securty firm?
3079
3080James Sutherland - Cypherglass.com
3081Preliminary, just 3 pages.  More to come
3082
3083Devin Lee KOREOS.IO
3084James Sutherland - Cypherglass.com
3085Preliminary, just 3 pages. More to come
3086Thanks.
3087
3088Craig Murray - EOS BlockSmith
3089another highly productive and this time extremely effecient meeting, thanks everyone!
3090
3091Nathan Rempel | GenerEOS Sydney
3092Timothy Lewis
3093Updated: https://gist.github.com/redjade/bdbcb10708e165b29d0301c5defa1d83
3094Have 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
3095Craig Murray - EOS BlockSmith
3096another highly productive and this time extremely effecient meeting, thanks everyone!
3097Yes agreed
3098@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
3099
3100Timothy Lewis
3101Nathan Rempel | GenerEOS Sydney
3102Have you been able to successfully execute these changes using the boot bios? I'm working on a similar fix now (not because i th
3103I'll DM you. May not fully solve the entire issue.
3104
3105Nathan Rempel | GenerEOS Sydney
3106Timothy Lewis
3107I'll DM you. May not fully solve the entire issue.
3108:+1:
3109
3110Tim Weston - GenerEOS (BP Sydney)
3111Hey guys, did we get a channel created to discus the voting portal etc ?
3112If not I’m happy to throw one up
3113
3114Marc-Antoine Ross - EOS Canadaadmin
3115All, 
3116
3117Thanks for another productive call!
3118
3119Find bellow the minutes, if you find anything not accurate, please suggest/comment and we will fix.
3120The raw log is included at the bottom of the document.
3121
3122https://docs.google.com/document/d/1HR16WF5nhNXNzkBh963ZKjSflsyBsMb0PsOhHSbQTsI
3123
3124Next steps June 7, 1300 UTC:
3125    Security report update - Dafeng EOS Asia
3126    ABP selection update - Kevin EOS New York
3127    Follow-up constitution 
3128    Review the current state of the UAT testing. Are people supplying proof of tests, adding tests, running tests
3129    More?
3130
3131Thanks, good after-mor-night!
3132
3133Google Docs
3134Go/NoGo June 7 0100 UTC
3135Go/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...
3136Marc-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»
3137Jk (Blockgenic)
3138Tim Weston - GenerEOS (BP Sydney)
3139Hey guys, did we get a channel created to discus the voting portal etc ?
3140Let me know if you do.
3141
3142Zhao Yu@ EOSLaoMao.com
3143Loading
3144and the group?
3145
3146Nathan Rempel | GenerEOS Sydney
3147Loading
3148Tim has to up his Telegram game 🤣
3149
3150Branden Espinoza
3151Tim, you ceated a channel, not a group.  That is for 1 way comms only.
3152
3153Tim Weston - GenerEOS (BP Sydney)
3154whoops will create now
3155
3156Nathan Rempel | GenerEOS Sydney
3157https://t.me/joinchat/IbfNrxA6yqKbzBXSXZxteA
3158
3159Tim Weston - GenerEOS (BP Sydney)
3160:point_up_2:🏻:point_up_2:🏻 here it is guys!
3161
3162Nathan Rempel | GenerEOS Sydney
3163Some fun messages from @daniellarimer
3164
3165Nathan Rempel | GenerEOS Sydney
3166Daniel LarimerJun 6, 2018 11:12:40 PM
3167I like how serious everyone is, but perfection is enemy of good enough
3168No, we wil run and live!
3169William 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!!!
3170I see people petrified by fear of unknown bugs. Life is messy. Be brave. We can overcome anything
3171Fortune favors the bold. And voters will notice.
3172I 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.
3173
3174Kyunghwan Kim - EOSeoul.io
3175Timothy Lewis
3176We are testing a fix. If it fixes, it will be brought up. If it doesn't we are comfortable launching incorrect.
3177Thank you! :+1:
3178
3179Ben Sigman
3180[Photo]
3181
3182Matthew Darwin - EOS Nation
3183Marc-Antoine Ross - EOS Canada
3184All, Thanks for another productive call! Find bellow the minutes, if you find anything not accurate, please suggest/comment a
3185Marc, thanks for the great notes!
3186
3187Roshan - EOS Authority
3188Marc-Antoine Ross - EOS Canada
3189All, Thanks for another productive call! Find bellow the minutes, if you find anything not accurate, please suggest/comment a
3190Thanks for the notes!
3191
3192Sandwich
3193Nathan Rempel | GenerEOS Sydney
3194I like how serious everyone is, but perfection is enemy of good enough
3195:fire:
3196Denis | EOS Nation invited Yves La Rose - EOS Nation
3197
3198Roman CryptoLions
3199Sam - EOS Dublin
3200@Bensig created a handy tracker for exactly that! https://status.producer.vote
3201nice
3202
3203Sharif Bouktila - EOS Dublinadmin
3204Next Validation Call is in 35 minutes 
3205
3206
3207 Security report update - Dafeng EOS Asia
3208 ABP selection update - Kevin EOS New York
3209 Follow-up constitution 
3210 Review the current state of the UAT testing. Are people supplying proof of tests, adding tests, running tests
3211 More?
3212
3213Either @marcantoineross or I will post Zoom link 5 minutes before call.
3214
3215Tim Weston - GenerEOS (BP Sydney)
3216:+1:
3217
3218Marc-Antoine Ross - EOS Canadaadmin
3219All,
3220
3221Here's the proposed agenda:
3222    Security report update - Dafeng EOS Asia
3223    ABP selection update - Kevin EOS New York
3224    Follow-up constitution 
3225    Review the current state of the UAT testing. Are people supplying proof of tests, adding tests, running tests
3226    More?
3227
3228https://zoom.us/j/438337388
3229
3230Zoom Video
3231Join our Cloud HD Video Meeting now
3232Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
3233Marc-Antoine Ross - EOS Canada pinned « All, Here's the proposed agenda: Security report update - Dafeng EOS Asia ABP selection update - Kevin EOS New York »
3234
3235Thomas "Disclaimer" Cox (all opinions mine)
3236Marc-Antoine Ross - EOS Canada
3237All, Here's the proposed agenda: Security report update - Dafeng EOS Asia ABP selection update - Kevin EOS New York
3238Reword "Follow-up constitution" to "follow-up on Constitution Article 9 Rollback Proposal" please?
3239
3240Marc-Antoine Ross - EOS Canadaadmin
3241done in the zoom chat
3242Marc-Antoine Ross - EOS Canada invited Miłosz Eos Emerge - Poland
3243
3244Brett Jeffery @ EOS the World
3245Nathan Rempel | GenerEOS Sydney
3246I like how serious everyone is, but perfection is enemy of good enough
3247:+1:
3248Elliot@EOS Pacific invited jason wang
3249
3250Nathan Rempel | GenerEOS Sydney
3251https://docs.google.com/spreadsheets/d/1gJnn0KS4rgDnTowPlN80gulVI77lRgldPhH17kZOnnI
3252
3253Google Docs
3254EOS Voting Portal Audit
3255About
3256
3257This spreadsheet is a list compiled by members of the EOS community( EMLG)
3258It is a list of all known EOS voting portals
3259This list is compile...
3260https://t.me/joinchat/IbfNrxA6yqKbzBXSXZxteA
3261
3262Kyunghwan Kim - EOSeoul.io
3263Timothy Lewis
3264We are testing a fix. If it fixes, it will be brought up. If it doesn't we are comfortable launching incorrect.
3265Being late, but finally got tested version of contracts for adjusting 1) token supply, 2) balance of system accounts, and 3) bancor state.
3266
3267https://github.com/eoseoul/eos-ramcost
3268
3269GitHub
3270eoseoul/eos-ramcost
3271eos-ramcost - Adjusting supply of a token and connector balance of bancor during final phase of boot.
3272
3273Nathan Rempel | GenerEOS Sydney
3274looks good to me, nice and clean. we''ll need this tested in boot sequence asap (12 hours)
3275
3276Alexandre Bourget - EOS Canada
3277Kyunghwan Kim - EOSeoul.io
3278Being late, but finally got tested version of contracts for adjusting 1) token supply, 2) balance of system accounts, and 3) ban
3279There 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.
3280
3281Nathan Rempel | GenerEOS Sydney
3282i looked at the cpps :(
3283Alexandre Bourget - EOS Canada
3284There 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
3285good catch
3286
3287Alexandre Bourget - EOS Canada
3288That was already voted on though..
3289
3290Nathan Rempel | GenerEOS Sydney
3291ok, i'll shelf it
3292
3293Thomas "Disclaimer" Cox (all opinions mine)
3294Strongly encourage all BPs who have done testing, to log their tests here:
3295
3296https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit#gid=1501553294
3297
3298Google Docs
3299EOS UAT - User Acceptance Testing
3300Home
3301
3302
3303Create a Case, Record a Test
3304Procedure 1: Create a Case
3305STEPS
33061, Confirm your case does not yet exist
3307a, Click the red Cases tab at the bo...
3308
3309Kyunghwan Kim - EOSeoul.io
3310Alexandre Bourget - EOS Canada
3311There 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
3312All 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?
3313
3314Ben Sigman
3315Alexandre Bourget - EOS Canada
3316That was already voted on though..
3317As I understand, there were no viable alternatives. Now that there is, don’t we want to offer it to the community?
3318
3319Kyunghwan Kim - EOSeoul.io
3320Alexandre Bourget - EOS Canada
3321There 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
3322If there is missing function in eosio.system.ramcost and eosio.token.ramcost with respective abi files, please tell me. It would be quite helpful.
3323
3324Alexandre Bourget - EOS Canada
3325This 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.
3326
3327I wouldn't go to war for this.
3328
3329Nathan Rempel | GenerEOS Sydney
3330Alexandre Bourget - EOS Canada
3331This proposition is quite complex (technically for code review, boot_seq adjustements, validation tools adjustments, and sociall
3332Concur at this stage
3333
3334Mr Fox
3335so， who can give a summary about what to do tomorrow?
3336thanks
3337
3338Kyunghwan Kim - EOSeoul.io
3339Okay. 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.
3340
3341Nathan Rempel | GenerEOS Sydney
3342Mr Fox
3343so， who can give a summary about what to do tomorrow?
3344instructions will be available pending the result of the go / no meeting
3345Kyunghwan Kim - EOSeoul.io
3346Okay. eos-ramcost is fully tested in my local environment. That is to explain and present tools that people requested and to get
3347I think it's fantastic work, the timing is just difficult
3348
3349Kyunghwan Kim - EOSeoul.io
3350Nathan Rempel | GenerEOS Sydney
3351I think it's fantastic work, the timing is just difficult
3352I have same opinion with you. :)
3353
3354Nathan Rempel | GenerEOS Sydney
3355I think anyone helping to solve issues for the launch and the community should be commended
3356
3357Mr Fox
3358Nathan Rempel | GenerEOS Sydney
3359instructions will be available pending the result of the go / no meeting
3360thanks
3361
3362deck - EOS New York
3363Everyone. 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?
3364https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=753803902
3365
3366Google Docs
3367EOS Mainnet Validation Plan
3368Validation Tools
3369
3370Name, Scope of Tests, BPs who will execute, How Long for Execution?
3371Firestarter from EOS Argentina, Injects csv, tool agnostic, sy...
3372
3373Sharif Bouktila - EOS Dublinadmin
3374deck - EOS New York
3375Everyone. I am treating the 4th criteria from the spreadsheet to mean that you need to send an overview of your security/tech sp
3376Yes
3377
3378Nathan Rempel | GenerEOS Sydney
3379deck - EOS New York
3380Everyone. I am treating the 4th criteria from the spreadsheet to mean that you need to send an overview of your security/tech sp
3381Fine for us
3382
3383Nate D - Aloha EOS
3384deck - EOS New York
3385Everyone. I am treating the 4th criteria from the spreadsheet to mean that you need to send an overview of your security/tech sp
3386:+1:
3387Miłosz Eos Emerge - Poland invited Krzysztof Manijak - EOSEmerge.io - Poland
3388
3389Timothy Lewis
3390Kyunghwan Kim - EOSeoul.io
3391Being late, but finally got tested version of contracts for adjusting 1) token supply, 2) balance of system accounts, and 3) ban
3392Awesome. @jemxpat @jaechung
3393Kyunghwan Kim - EOSeoul.io
3394Okay. eos-ramcost is fully tested in my local environment. That is to explain and present tools that people requested and to get
3395This was really well done. I commend you for the effort, regardless of outcome.
3396
3397David Moss
3398+1
3399
3400Marc-Antoine Ross - EOS Canadaadmin
3401All, 
3402
3403Thanks for an amazing call!
3404
3405Find bellow the minutes, if you find anything not accurate, please suggest/comment and we will fix.
3406The todo for next call is included in the minutes
3407The raw log is included at the bottom of the document.
3408
3409https://docs.google.com/document/d/1Fpevju50lpXDH50dMH0A4NOUnUioHb7xYy76RQXG1w4
3410
3411Next call June 8, 0100 UTC
3412
3413Thanks, good after-mor-night!
3414
3415Google Docs
3416Validation Call June 7 1300 UTC
3417Validation 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...
3418Marc-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»
3419
3420David Moss
3421Marc-Antoine Ross - EOS Canada
3422All, Thanks for an amazing call! Find bellow the minutes, if you find anything not accurate, please suggest/comment and we wi
3423Thanks @marcantoineross and team!
3424
3425Jose Toriello
3426Someone leaked minutes...
3427
3428Jose Toriello
3429Eduardo CuevasJun 7, 2018 11:10:25 AM
3430https://www.trustnodes.com/2018/06/06/eos-launch-delayed-pending-audit-results
3431
3432Trustnodes
3433EOS Launch Delayed Pending Audit Results
3434A 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...
3435
3436Nathan Rempel | GenerEOS Sydney
3437neat we can reverse blocks at will
3438apparently
3439
3440Craig Murray - EOS BlockSmith
3441@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?
3442@DavidMoss perhaps you have comment on this as well?
3443
3444Nathan Rempel | GenerEOS Sydney
3445Craig Murray - EOS BlockSmith
3446@eosnewyork is one of the questions we're asking the abp candidates to provide "what method of injection are you using and is it
3447don't think its possible for @eosnewyork to make a decision based on boot method
3448
3449Kevin Rose - EOS New York
3450Craig Murray - EOS BlockSmith
3451@eosnewyork is one of the questions we're asking the abp candidates to provide "what method of injection are you using and is it
3452I 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.
3453
3454Nathan Rempel | GenerEOS Sydney
3455as long as the chain is validated it could be hand bombed i think
3456
3457Craig Murray - EOS BlockSmith
3458we've argued about ram for a while now, do we even know what method one of these 16 people will use?
3459
3460Kevin Rose - EOS New York
3461Craig Murray - EOS BlockSmith
3462we've argued about ram for a while now, do we even know what method one of these 16 people will use?
3463I don’t think that is up to the ABP.
3464Have we tested JEMs RAM option that rounds to a perfect 1BB?
3465
3466Michael Yeates
3467we have that on our chain now
3468
3469Craig Murray - EOS BlockSmith
3470what is the github link?
3471
3472Michael Yeates
3473to our chain?
3474
3475Craig Murray - EOS BlockSmith
3476to the tool used to inject it, JEM's option
3477
3478Michael Yeates
3479ill get it for you
3480
3481Kevin Rose - EOS New York
3482We have until 1600 UTC to input ABP required criteria.
3483I don’t want this process to hold up a go/no-go decision at 0100
3484
3485Jae Chung - HKEOS
3486Craig Murray - EOS BlockSmith
3487to the tool used to inject it, JEM's option
3488https://github.com/HKEOS/Ghostbusters-Testnet/tree/master/chain-validator
3489was sent ~3 days ago
3490
3491GitHub
3492HKEOS/Ghostbusters-Testnet
3493Ghostbusters-Testnet - EOS Core- an EOS mainnet launch solution
3494
3495Craig Murray - EOS BlockSmith
3496it'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
3497
3498Kevin Rose - EOS New York
3499Craig Murray - EOS BlockSmith
3500it's like 90% of what the ABP does... the other 10% staying alive... and there has been heaps of fighting about ram solutions, j
3501Like I said, I think that any ABP that is applying for this position is consenting to the community approved process.
3502
3503Craig Murray - EOS BlockSmith
3504Kevin Rose - EOS New York
3505Like I said, I think that any ABP that is applying for this position is consenting to the community approved process.
3506then we need a community approved process pretty quick!
3507
3508Kevin Rose - EOS New York
3509Put 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.
3510
3511Craig Murray - EOS BlockSmith
351216 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?
3513
3514Sheldon | EOShenzhen
3515Jae Chung - HKEOS
3516https://github.com/HKEOS/Ghostbusters-Testnet/tree/master/chain-validator was sent ~3 days ago
3517this is really awesome
3518
3519Craig Murray - EOS BlockSmith
3520Kevin Rose - EOS New York
3521Put 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
3522I have added criteria
3523
3524Kevin Rose - EOS New York
3525Craig Murray - EOS BlockSmith
352616 candidates, i really like everyone's entheusiasm. Personally I think there is a very short list of people that should be doi
3527If they fail I propose we go back to the list of applicants. But that’s just my opinion.
3528
3529Craig Murray - EOS BlockSmith
3530Jae Chung - HKEOS
3531https://github.com/HKEOS/Ghostbusters-Testnet/tree/master/chain-validator was sent ~3 days ago
3532thx
3533
3534Alex - EOS SOCAL
3535Kevin Rose - EOS New York
3536If they fail I propose we go back to the list of applicants. But that’s just my opinion.
3537Agreed
3538
3539Craig Murray - EOS BlockSmith
3540well 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
3541i recommend we figure that out before the abp is chosen
3542
3543Sukesh Tedla (EOSGreen)
3544Where can one find the list of ABP candidates? I cannot find that in the document, should we add it to the doc?
3545
3546Kevin Rose - EOS New York
3547Sukesh Tedla (EOSGreen)
3548Where can one find the list of ABP candidates? I cannot find that in the document, should we add it to the doc?
3549It is secret to avoid security risks and merchandizing the responsibility to the token holders.
3550Eric_EOSARMY.io invited phajek eosarmy Patrick
3551
3552Kevin Rose - EOS New York
3553The BPCs present on the previous 1300 UTC asked that EOS New York field and manage the list with David Moss as a witness.
3554Miłosz Eos Emerge - Poland invited Marek EOSEmerge.io - Poland
3555
3556Nate D - Aloha EOS
3557Craig Murray - EOS BlockSmith
3558well 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
3559I don't think the how matters, as long as the data state matches what everyone expects and tests pass.
3560
3561Craig Murray - EOS BlockSmith
3562Nate D - Aloha EOS
3563I don't think the how matters, as long as the data state matches what everyone expects and tests pass.
3564so we leave it up to the abp to decide then?
3565Sukesh Tedla (EOSGreen)
3566Where can one find the list of ABP candidates? I cannot find that in the document, should we add it to the doc?
3567we have suspended radical transparency and the list is hidden, as will be the name of the anon abp
3568
3569Sukesh Tedla (EOSGreen)
3570Kevin Rose - EOS New York
3571The BPCs present on the previous 1300 UTC asked that EOS New York field and manage the list with David Moss as a witness.
3572Sorry! I wasn't able to join the meeting. I don't know what was discussed but we wanted to go with the consensus decision.
3573
3574Nate D - Aloha EOS
3575Craig Murray - EOS BlockSmith
3576so we leave it up to the abp to decide then?
3577The process they use to boot? Yes, I think so.
3578
3579Craig Murray - EOS BlockSmith
3580the 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
3581
3582Nate D - Aloha EOS
3583We 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.
3584
3585Sukesh Tedla (EOSGreen)
3586Nate D - Aloha EOS
3587We 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
3588+1
3589
3590Craig Murray - EOS BlockSmith
3591there are 2 tools that I know of, Igor has one that uses eosjs.  Alex has one that uses golang.
3592Nate D - Aloha EOS
3593We 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
3594did we?  I'm sorry I'm trying to catch up on the details i missed some of the meeting
3595and this method is currently expressed in Igor's repo that was linked earlier?
3596
3597Nate D - Aloha EOS
3598Craig Murray - EOS BlockSmith
3599did we? I'm sorry I'm trying to catch up on the details i missed some of the meeting
3600Yes, I'd have to dig up when exactly but it was 2-3 meetings ago.
3601
3602Craig Murray - EOS BlockSmith
3603Jae Chung - HKEOS
3604https://github.com/HKEOS/Ghostbusters-Testnet/tree/master/chain-validator was sent ~3 days ago
3605forgive 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?
3606Nate D - Aloha EOS
3607Yes, I'd have to dig up when exactly but it was 2-3 meetings ago.
3608I'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
3609but please if you have minutes that would be great, i would be thrilled if this was actually already resolved
3610
3611Nate D - Aloha EOS
3612Yeah I'm looking...
3613https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c/edit
3614
3615Google Docs
3616GoNoGo Call
3617Wednesday 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...
3618
3619Kevin Rose - EOS New York
3620Can someone share the testing doc with with Dan Larimer?
3621
3622Craig Murray - EOS BlockSmith
3623https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=668547189
3624
3625Google Docs
3626EOS Mainnet Validation Plan
3627Validation Tools
3628
3629Name, Scope of Tests, BPs who will execute, How Long for Execution?
3630Firestarter from EOS Argentina, Injects csv, tool agnostic, sy...
3631i've sent him that one, i think there is also another one
3632
3633Kevin Rose - EOS New York
3634Craig Murray - EOS BlockSmith
3635i've sent him that one, i think there is also another one
3636Thank you
3637
3638Craig Murray - EOS BlockSmith
3639there is also Thomas's one, but i honestly haven't had time to look at it, i dont have a link handy
3640
3641Josh Kauffman - EOS Canada
3642https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit#gid=1501553294
3643
3644Google Docs
3645EOS UAT - User Acceptance Testing
3646Home
3647
3648
3649Create a Case, Record a Test
3650Procedure 1: Create a Case
3651STEPS
36521, Confirm your case does not yet exist
3653a, Click the red Cases tab at the bo...
3654^^ Daniel
3655Craig Murray - EOS BlockSmith
3656I'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
3657On 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.
3658
3659Craig Murray - EOS BlockSmith
3660Ok so @jemxpat is ok with this?  @jaechung and @michaelyeates and @igorls and @xebb82 and @trustlayer are all ok with this?
3661to be clear i do not care at all what method is used I'm just trying to avoid conflict after an abp is chosen
3662
3663Michael Yeates
3664please can we put this on the agenda for the next meeting
3665
3666Marc-Antoine Ross - EOS Canadaadmin
3667How the chain is booted does not matter as much as validation of its content.
3668
3669We have consensus on the content of the chain, as per the minutes. Look for "Question (21:50:00)" and the notes following.
3670https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c
3671
3672Google Docs
3673GoNoGo Call
3674Wednesday 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...
3675
3676Craig Murray - EOS BlockSmith
3677ok.  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?
3678
3679Marc-Antoine Ross - EOS Canadaadmin
3680Craig Murray - EOS BlockSmith
3681ok. To be clear, my understanding is now that we have consensus that eos.io should issue an extra approx 19k tokens and they be
3682Correct
3683
3684Yves La Rose - EOS Nation
3685This was the consensus yesterday, yes.
3686
3687Timothy Lewis
3688Craig Murray - EOS BlockSmith
3689@eosnewyork is one of the questions we're asking the abp candidates to provide "what method of injection are you using and is it
3690I like this.
3691Craig Murray - EOS BlockSmith
3692ok. To be clear, my understanding is now that we have consensus that eos.io should issue an extra approx 19k tokens and they be
3693If 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.
3694
3695Craig Murray - EOS BlockSmith
3696Timothy Lewis
3697If a solution is found and presented, it may be considered. I do not know if we could reach consensus on the change, but @resver
3698Per 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
3699
3700mini - EOS Argentina
3701Timothy Lewis
3702If a solution is found and presented, it may be considered. I do not know if we could reach consensus on the change, but @resver
3703We 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  :) 
3704
3705We should delay thing only for critical things. Otherwise we are in an infinite loop reaching for perfection
3706
3707Sharif Bouktila - EOS Dublinadmin
3708We know how to validate the chain using a variety of tools. 
3709
3710Let @eosnewyork and @DavidMoss figure it out.
3711
3712If that chain gets to 15% we are in business.  If not we start again.
3713
3714Denis | EOS Nation
3715Daniel LarimerJun 7, 2018 12:11:55 PM
3716We are preparing a 1.0.2 update that will fix things with the optional whitelist/blacklist for contracts
3717
3718Craig Murray - EOS BlockSmith
3719Sharif Bouktila - EOS Dublin
3720We know how to validate the chain using a variety of tools. Let @eosnewyork and @DavidMoss figure it out. If that chain gets
3721we 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
3722Denis | EOS Nation
3723We are preparing a 1.0.2 update that will fix things with the optional whitelist/blacklist for contracts
3724yup, and then there's that to add to the mix :smile:
3725this 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
3726
3727Sharif Bouktila - EOS Dublinadmin
3728Ok - We have a process , I suggest we put it on the agenda at 01:00 UTC 
3729
3730@jemxpat @michaelyeates @trustlayer @abourget @marcantoineross 
3731
3732I propose result of next vote is set in stone.  
3733
3734Agreed?
3735
3736Craig Murray - EOS BlockSmith
3737i 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
3738
3739Sharif Bouktila - EOS Dublinadmin
3740Reason 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
3741
3742Jae Chung - HKEOS
3743@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?
3744
3745Sharif Bouktila - EOS Dublinadmin
3746We are starting a new chain anyway aren’t we?
3747
3748Jae Chung - HKEOS
3749this is something important for all of us to know for mainnet— it means minimum catch up time for LIB is ~3 minutes
3750
3751Denis | EOS Nation
3752Craig Murray - EOS BlockSmith
3753yup, and then there's that to add to the mix :smile:
3754Since we are already doing a reset on the chain, it might be something to consider.
3755
3756I have no preference, 1.0.1 or 1.0.2 is fine with me (preference to 1.0.2 if we have concensus)
3757
3758Jae Chung - HKEOS
3759Denis | EOS Nation
3760Since 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
3761so you do have a preference ;)
3762
3763Denis | EOS Nation
3764Sharif Bouktila - EOS Dublin
3765We are starting a new chain anyway aren’t we?
3766Yes, new chain is required because of constitution changes (for legal reasons)
3767Jae Chung - HKEOS
3768so you do have a preference ;)
3769I vote :+1: for both
3770
3771mini - EOS Argentina
377221*12*2/3
3773@jaechung
3774
3775Denis | EOS Nation
3776Jae Chung - HKEOS
3777so you do have a preference ;)
3778It's a patch update, no feature changes, so it shouldn't be an issue if we do or do not use it
3779
3780Sharif Bouktila - EOS Dublinadmin
3781Denis | EOS Nation
3782Yes, new chain is required because of constitution changes (for legal reasons)
3783I agree we should,  but don’t quite understand that as we will be able to change constitution later.
3784
3785Denis | EOS Nation
3786Jae Chung - HKEOS
3787so you do have a preference ;)
3788Jae, do you have time to look into it? I'll support your judgement
3789
3790Jae Chung - HKEOS
3791Denis | EOS Nation
3792Jae, do you have time to look into it? I'll support your judgement
3793yep, we're looking into it now but at the moment I agree with you— preference for 1.0.2
3794
3795Craig Murray - EOS BlockSmith
3796Sharif Bouktila - EOS Dublin
3797I agree we should, but don’t quite understand that as we will be able to change constitution later.
3798only 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
3799
3800Sharif Bouktila - EOS Dublinadmin
3801Craig Murray - EOS BlockSmith
3802only before 15%, and even then it's a little sketchy... we're validating the chain, everything. Once that's done it can't chang
3803Thanks
3804
3805Denis | EOS Nation
3806Sharif Bouktila - EOS Dublin
3807I agree we should, but don’t quite understand that as we will be able to change constitution later.
3808We are recompiling the eosio.system ABI, this needs to be loaded in the initial boot sequence.
3809
3810Craig Murray - EOS BlockSmith
3811if we're doing a new chain, 1.0.2 yes :+1:
3812
3813Denis | EOS Nation
3814Jae Chung - HKEOS
3815yep, we're looking into it now but at the moment I agree with you— preference for 1.0.2
3816:+1: perfect
3817
3818Jae Chung - HKEOS
3819mini - EOS Argentina
382021*12*2/3
3821Thanks. 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:
3822
3823mini - EOS Argentina
3824Yes shouldn't be 325, don't know if has anything to do with the boot process.
3825Or a bug :/
3826
3827Craig Murray - EOS BlockSmith
3828Jae Chung - HKEOS
3829Thanks. 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
3830yes Dan confirmed normal operation was that, or higher
3831
3832Thomas "Disclaimer" Cox (all opinions mine)
3833FYI, I'm still finishing off the article expressing the case for reverting Article IX. Team is reviewing now.
3834
3835Craig Murray - EOS BlockSmith
3836all the eos-bios launches stage 1 to 20 ran that way as well 300-400 lib behind head
3837
3838Zhao Yu@ EOSLaoMao.com
3839Just want to mention that the new chain will honor unregistered users right?
3840
3841Jae Chung - HKEOS
3842mini - EOS Argentina
3843Yes shouldn't be 325, don't know if has anything to do with the boot process.
3844The LIB updates in logs every time you go to the next  producer, it looks something like this:
3845ncy: 3989 ms]
38461385989ms 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]
38471386492ms 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]
38481386988ms 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]
38491387488ms 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]
38501387989ms 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]
38511388488ms 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
3852ncy: 3989 ms]
38531388989ms 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]
38541389490ms 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]
38551389989ms 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]
38561390488ms 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]
38571390988ms 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]
38581391488ms 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]
3859I wouldn't be so fast to call it a problem in the boot process or a bug in the software @moonxor ;)
3860
3861Craig Murray - EOS BlockSmith
3862yes lib moves at the end of the producers turn, but still follows behind getting it's 15/21 signatures to be lib
3863
3864mini - EOS Argentina
3865I said I didn't know
3866
3867Marc-Antoine Ross - EOS Canadaadmin
3868Zhao Yu@ EOSLaoMao.com
3869Just want to mention that the new chain will honor unregistered users right?
3870Yes
3871
3872Zhao Yu@ EOSLaoMao.com
3873Got some holders who forget to register asking, so just want to make sure
3874
3875Craig Murray - EOS BlockSmith
3876Zhao Yu@ EOSLaoMao.com
3877Got some holders who forget to register asking, so just want to make sure
3878yes 100%
3879
3880Nate D - Aloha EOS
3881What 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?
3882
3883Craig Murray - EOS BlockSmith
3884Nate D - Aloha EOS
3885What about unregistered holders that had erc20 EOS in an ETH wallet where that wallet never sent any ETH or EOS? Was the issue o
3886i 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
3887
3888Thomas "Disclaimer" Cox (all opinions mine)
3889It 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.
3890
3891https://forums.eosgo.io/discussion/1189/the-case-for-reverting-article-ix-9/p1?new=1
3892
3893EOS Go
3894The Case for Reverting Article IX (9)
3895This article explains why Article IX (9) "Dispute Resolution" should have the changes of 30-May-2018 reverted. Situation
3896This is the write-up I promised on the 0100 call
3897Ben Sigman invited Kartik Mandaville | SpringRole
3898
3899Ben Sigman
3900Kevin Rose - EOS New York
3901Put 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
3902Where is this list?
3903
3904Josh Kauffman - EOS Canada
3905If you check the notes from today's call, there should be links in there
3906@Bensig https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c
3907
3908Google Docs
3909GoNoGo Call
3910Wednesday 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...
3911
3912Ben Sigman
3913Josh Kauffman - EOS Canada
3914If you check the notes from today's call, there should be links in there
3915Thank you
3916Josh Kauffman - EOS Canada
3917If you check the notes from today's call, there should be links in there
3918Actually, I do not see any links in there for documents.
3919
3920Josh Kauffman - EOS Canada
3921Shoot that's my bad, I grabbed the one from yesterday's call. One sec, gonna get the right link.
3922https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=753803902
3923
3924Google Docs
3925EOS Mainnet Validation Plan
3926Validation Tools
3927
3928Name, Scope of Tests, BPs who will execute, How Long for Execution?
3929Firestarter from EOS Argentina, Injects csv, tool agnostic, sy...
3930that's the one that has the ABP criteria
3931
3932Roshan - EOS Authority
3933Daniel LarimerJun 7, 2018 2:46:12 PM
3934Just 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.
3935
3936Sharif Bouktila - EOS Dublinadmin
3937For 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. 
3938
3939One 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.
3940
3941Timothy Lewis
3942Sharif Bouktila - EOS Dublin
3943Ok - We have a process , I suggest we put it on the agenda at 01:00 UTC @jemxpat @michaelyeates @trustlayer @abourget @marcant
3944Excited.
3945
3946Jae Chung - HKEOS
3947https://github.com/EOSIO/eos/issues/3917
3948GitHub
3949Assertion exception on get accounts #3917
3950OS: 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...
3951https://github.com/EOSIO/eos/issues/3918
3952GitHub
3953Transfer action does not work at times #3918
3954LIB was moving with head block quite closely (within 400), and the transfer action was pushed multiple times. However, none of these transfers seem to...
3955found some things while testing in the last couple of hours which we've filed
3956seems like they should be addressed soon, #3918 could be critical
3957
3958Denis | EOS Nation
3959Jae Chung - HKEOS
3960found some things while testing in the last couple of hours which we've filed
3961:+1:Thanks for sharing Jae, great finds, at least using the -j flag can workaround this issue (for now until resolved)
3962
3963Jae Chung - HKEOS
3964Denis | EOS Nation
3965:+1:Thanks for sharing Jae, great finds, at least using the -j flag can workaround this issue (for now until resolved)
3966yep, and I think Dan will solve #3917 with tomorrow's 1.0.2 release
3967
3968Kyle - EOSVibes
3969Thomas "Disclaimer" Cox (all opinions mine)
3970It is the shared belief of the Arbitration Team and of me, Thomas, that the last-minute change to Article IX be reverted. This c
3971Boom!:boom: Good on yea Tom cat! :white_check_mark:
3972I’m very happy to see this (apologies for the over-enthusiastic response) :blush:
3973
3974Jae Chung - HKEOS
3975but #3918 needs attention, it could be quite dangerous
3976
3977Denis | EOS Nation
3978Jae Chung - HKEOS
3979but #3918 needs attention, it could be quite dangerous
3980🤔I agree with Dan's comment, not too sure if that's a bug in cleos or network forks/local node environment.
3981
3982Dan tagged it as "support" (might not be a bug)
3983
3984Alexandre Bourget - EOS Canada
3985Yeah I remember experiencing that when some nodes were not fully sync'd ...
3986it's quite surprising, though !
3987We also found that, depending on network topology, setting p2p-max-nodes-per-host helps..
3988we were often trying to connect many times to a node from the same office IP.. so some wouldn't be sync'd..
3989but it wasn't immediately obvious
3990Jason Wang - EOS Pacific joined group via invite link
3991Dr Ye EOS WashingtonDC - TChain joined group via invite link
3992Dr Ye EOS WashingtonDC - TChain
3993kicking .. just prevent from being kicked out again :-)
3994Is 597a still the only mainnet candidate as we voted two days ago? sorry missed the latest status
3995
3996Marc-Antoine Ross - EOS Canadaadmin
3997Dr Ye EOS WashingtonDC - TChain
3998Is 597a still the only mainnet candidate as we voted two days ago? sorry missed the latest status
3999No, there will be a new chain launched by the anonymous ABP
4000Dr Ye EOS WashingtonDC - TChain
4001ok. just let us know the new genesis and peer list
4002Jason Wang - EOS Pacific
4003Marc-Antoine Ross - EOS Canada
4004No, there will be a new chain launched by the anonymous ABP
4005do you knwo if we have anonymous ABP selected already?
4006
4007Timothy Lewis
4008Jason Wang - EOS Pacific
4009do you knwo if we have anonymous ABP selected already?
4010Not yet
4011
4012David P - EOS42
4013Timothy Lewis
4014Not yet
4015Can ask Kevin Rose shortly he’ll be arriving at Tulip in about half an hour
4016But yes not yet we’ll get an update on the call in 3hrs
4017
4018Douglas Horn | EOSAmericas
4019For 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.
4020Please 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.
4021Dr Ye EOS WashingtonDC - TChain
4022zoom link for the call?
4023
4024Marc-Antoine Ross - EOS Canadaadmin
4025All,
4026
4027For internal use only for the EOS Validation (EMLG) Telegram Channel. Please do not share outside of this channel.
4028
4029Here's the proposed agenda:
4030
4031Re-ratify on next call the 2/3+1 for Go/NoGo
4032Constitution change vote + update on changes
4033ABP selection update
4034No P0 P1 reported?
4035Voting Portal update
4036Go/NoGO vote
403748 hour update + coordination of the announcements
4038
4039https://zoom.us/j/326472166
4040
4041Zoom Video
4042Join our Cloud HD Video Meeting now
4043Zoom is the leader in modern enterprise video communications, with an easy, reliable cloud platform for video and audio conferencing, chat, and webina...
4044Marc-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»
4045
4046deck - EOS New York
4047Douglas Horn | EOSAmericas
4048Please 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
4049Hey 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
4050
4051Rick Schlesinger - EOS New York
4052please dont forward the zoom link
4053
4054Douglas Horn | EOSAmericas
4055deck - EOS New York
4056Hey 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
4057Yes, 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.
4058Rick Schlesinger - EOS New York
4059please dont forward the zoom link
4060We're not forwarding it. It's to our team member.
4061
4062Rohan - EOSauthority
4063Rick Schlesinger - EOS New York
4064please dont forward the zoom link
4065Ok
4066
4067Rick Schlesinger - EOS New York
4068im saying dont forward it to public channels. you can provide to your team members of course.
4069
4070Rohan - EOSauthority
4071Is the link out yet?
4072
4073Douglas Horn | EOSAmericas
4074:+1:
4075
4076Rohan - EOSauthority
4077Can’t find it anywhere?
4078
4079Rick Schlesinger - EOS New York
4080scroll up about 7 lines
4081
4082Rohan - EOSauthority
4083Rick Schlesinger - EOS New York
4084scroll up about 7 lines
4085I think it’s my 2AM brain. Thanks.
4086
4087Alexandre Bourget - EOS Canada
4088@daniellarimer hey Dan, what would be the impact of transfering all EOS out the eosio.ram and eosio.ramfee accounts, before eosio resignation ?
4089
4090Daniel Larimer
4091Ram is used by market maker
4092Ramfee is at community disposal
4093
4094Roman CryptoLions
4095@jemxpat
4096
4097jem
4098Alexandre Bourget - EOS Canada
4099@daniellarimer hey Dan, what would be the impact of transfering all EOS out the eosio.ram and eosio.ramfee accounts, before eosi
4100No user "gifted" with ram would be able to sell until some other user buys new ram post 15% activation. Tested.
4101
4102Daniel Larimer
4103jem
4104No user "gifted" with ram would be able to sell until some other user buys new ram post 15% activation. Tested.
4105It violates bancor algorithm invariant
4106
4107Kyunghwan Kim - EOSeoul.io
4108transfer 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.
4109
4110and transfer of token doesn’t impact the supply of token, also.
4111
4112jem
4113KHKim is correct. There is no violation of Bancor with this method.
4114
4115Daniel Larimer
4116Kyunghwan Kim - EOSeoul.io
4117transfer of token doesn’t impact price of ram. price of ram is determined in bancor state in rammarket db only through buy/sellr
4118It prevents market maker from filling orders
4119
4120jem
4121Only until new user buys ram.
4122
4123David Moss
4124Dan, we need a comment on https://github.com/EOSIO/eos/issues/3918
4125GitHub
4126Transfer action does not work at times #3918
4127LIB was moving with head block quite closely (within 400), and the transfer action was pushed multiple times. However, none of these transfers seem to...
4128Marshall - SaltBlock invited Robrigo - EOS Detroit
4129
4130Robrigo - EOS Detroit
4131Thanks for the add @marshallslc.
4132
4133Marshall - SaltBlock
4134You're welcome
4135
4136Andrey Marchuk
4137Tulip conf cannot join back because of 200 participants limits
4138
4139Thomas "Disclaimer" Cox (all opinions mine)
4140TRY AGAIN in a few minutes
4141
4142Ben Sigman
4143https://docs.google.com/spreadsheets/d/1gJnn0KS4rgDnTowPlN80gulVI77lRgldPhH17kZOnnI/edit#gid=744644035
4144
4145Google Docs
4146EOS Voting Portal Audit
4147About
4148
4149This spreadsheet is a list compiled by members of the EOS community( EMLG)
4150It is a list of all known EOS voting portals
4151This list is compile...
4152
4153Alexandre Bourget - EOS Canada
4154@daniellarimer do you think it makes sense to create an eosio.burned account, where we can put things in ?
4155If you're planning a recall action, maybe it's useless..
4156
4157Chitty 🅑 - EOS Argentina
4158Is phill from eos switzerland here?.. I am just wondering if they are a bp since I havent seen them before
4159
4160Jose Toriello
4161Chitty 🅑 - EOS Argentina
4162Is phill from eos switzerland here?.. I am just wondering if they are a bp since I havent seen them before
4163Good question
4164Heejae - EOSYS.io
4165Chitty 🅑 - EOS Argentina
4166Is phill from eos switzerland here?.. I am just wondering if they are a bp since I havent seen them before
4167Me too.
4168
4169Chitty 🅑 - EOS Argentina
4170I think there are a couple of fake bps in the chat
4171
4172Igor Lins e Silva - EOS Rio
4173Chitty 🅑 - EOS Argentina
4174I think there are a couple of fake bps in the chat
4175:+1:
4176
4177Rick Schlesinger - EOS New York
4178do the vote here?
4179
4180J.T. - EOS the World
4181Yes.
4182Or post a new straw poll here.
4183An Byung Chan - EOSYS invited Lievin Kim - EOSYS
4184
4185David P - EOS42
4186I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4187Ricardo Marlière - EOS Brazil invited EOS - Antarctica
4188
4189Ross (EOSphere)
4190Was thinking the same
4191
4192mini - EOS Argentina
4193David P - EOS42
4194I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4195Me neither
4196
4197Chitty 🅑 - EOS Argentina
4198he is fake, and looks like a troll
4199
4200J.T. - EOS the World
4201agreed.
4202Pascal Van Wy | EOS Network by Advanced Blockchain AG
4203agreed
4204
4205Patrick B - Aloha EOS
4206He's definitely trolling
4207
4208Rohan - EOSauthority
4209David P - EOS42
4210I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4211Good find..
4212
4213Rick Schlesinger - EOS New York
4214David P - EOS42
4215I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4216+1
4217
4218Alex - EOS SOCAL
4219David P - EOS42
4220I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4221+1
4222
4223Hubert Chang-EOSeoul.io
4224Can we kick him out from the call?
4225
4226Jacky - JEDA
4227David P - EOS42
4228I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4229+1
4230David P - EOS42
4231I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4232+1
4233David P - EOS42
4234I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4235+1
4236
4237David P - EOS42
4238Yes please
4239And various others who are clear no’s
4240
4241Khosi Morafo eosAfrica
4242David P - EOS42
4243I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4244+1
4245
4246Denis | EOS Nation
4247+1 for ELMG voting
4248
4249Andrey Marchuk
4250+1
4251
4252Kevin Rose - EOS New York
4253David P - EOS42
4254I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4255+1
4256
4257Craig Murray - EOS BlockSmith
4258+1
4259Ben Sigman invited Kurt Braget | White Rabbit ICOs
4260Bean@EOS Cannon
4261+1
4262Pascal Van Wy | EOS Network by Advanced Blockchain AG
4263+1
4264jem invited Nick eos.fish
4265
4266Cryptosufi - 威杰 - BitSpace
4267David P - EOS42
4268I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4269+1
4270
4271Eric - sw/edenadmin
4272Can we postpone the vote until 13:00 and have some tool ready?
4273Nick eos.fish
4274Thank you Jem!
4275
4276Denis | EOS Nation
4277Eric - sw/eden
4278Can we postpone the vote until 13:00 and have some tool ready?
4279:-1:
4280
4281Issay@OracleChain
4282Nick eos.fish
4283Thank you Jem!
4284+1
4285
4286Douglas Horn | EOSAmericas
4287Eric - sw/eden
4288Can we postpone the vote until 13:00 and have some tool ready?
4289:-1:
4290Nick eos.fish
4291David P - EOS42
4292I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
4293+1
4294
4295Chitty 🅑 - EOS Argentina
4296Eric - sw/eden
4297Can we postpone the vote until 13:00 and have some tool ready?
4298we have most bps online now, lets vote
4299
4300Cryptosufi - 威杰 - BitSpace
4301Eric - sw/eden
4302Can we postpone the vote until 13:00 and have some tool ready?
4303We could start cleos voting, until audited tools arrive.
4304
4305Eric - sw/edenadmin
4306I'm up for whatever, this just feels like a farce...
4307
4308Rohan - EOSauthority
4309Please stop posting messages.. wait for Sharif’s question and then vote..
4310
4311Josh Kauffman - EOS Canada
4312-----------------------------------------------------------------------------------------------------------------------------
4313PLEASE DO NOT WRITE ANYTHING BELOW THIS UNTIL THOMAS HAS POSTED THE QUESTION IN THIS CHANNEL
4314-----------------------------------------------------------------------------------------------------------------------------
4315
4316Thomas "Disclaimer" Cox (all opinions mine)
4317[Sharif will post the question]
4318Loading
4319You need permission
4320This form can only be viewed by users in the owner's organization.
4321
4322Sharif Bouktila - EOS Dublinadmin
4323Please confirm using GO/ NO GO to launch at 13:00 UTC 8th June 2018 using current release.
4324
4325Denis | EOS Nation
4326No need for form
4327
4328Cryptosufi - 威杰 - BitSpace
4329Go
4330
4331Sebastian Castro - EOS Argentina 🇦🇷
4332Go
4333
4334Ralf Weinand | GenerEOS (BP Sydney)
4335Go
4336
4337James Sutherland - Cypherglass.com
4338Go
4339
4340Rohan - EOSauthority
4341Sharif Bouktila - EOS Dublin
4342Please confirm using GO/ NO GO to launch at 13:00 UTC 8th June 2018 using current release.
4343Go - EOS Authority
4344
4345Alex - EOS SOCAL
4346Go
4347
4348Nate D - Aloha EOS
4349GO
4350
4351Marek EOSEmerge.io - Poland
4352GO
4353
4354Domi - EOS Rio
4355the abp wasn't even selected, poor him if it's a go
4356
4357EOS - Antarctica
4358No go.
4359
4360zhangzc | Onechain
4361GO
4362
4363Jose Toriello
4364Go
4365
4366Craig Murray - EOS BlockSmith
4367go
4368
4369Andrey Marchuk
4370Go - BlockEOS.io
4371
4372Jorge Ferrando - EOSMetal
4373Go
4374
4375Denis | EOS Nation
4376GO
4377
4378Ross (EOSphere)
4379Go
4380
4381crazybit@SuperONE.io
4382Go Go Go
4383
4384Marshall - SaltBlock
4385Go
4386
4387deck - EOS New York
4388go
4389
4390Kedar Iyer | LibertyBlock
4391GO
4392Nick eos.fish
4393Go
4394
4395Joshua Qiu @EOSeco
4396Go
4397Robert DeWilder - Worbli
4398go
4399
4400Miłosz Eos Emerge - Poland
4401Go
4402
4403Sharif Bouktila - EOS Dublinadmin
4404No Go
4405
4406Eric - sw/edenadmin
4407No Go
4408Jason Wang - EOS Pacific
4409Go
4410
4411Jialin Li - EOS WTZ
4412Go
4413
4414jem
4415jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet
4416No Go
4417
4418Hugo Yang - EOS Silicon Valley
4419No go
4420
4421Timothy Lewis
4422No go
4423
4424Issay@OracleChain
4425NO GO
4426
4427Igor Lins e Silva - EOS Rio
4428No go
4429
4430Basit Raza - EOSVibes
4431GO
4432
4433Marc-Antoine Ross - EOS Canadaadmin
4434Go
4435
4436ndoy |EOS Cafe: Calgary |
4437GO
4438
4439Ian(Yahuang Wu) - MEET.ONE
4440NO GO.
4441
4442Pete BlockMatrix
4443no go
4444
4445Zhao Yu@ EOSLaoMao.com
4446GO
4447
4448Ricardo Marlière - EOS Brazil
4449no go... why the rush? 1.0.2 is not even out
4450
4451Jacky - JEDA
4452GO
4453
4454Celu - Blockgenic
4455Go
4456
4457zhangzc | Onechain
4458GO
4459
4460J.T. - EOS the World
4461No Go.
4462
4463Ravi (Blockpro.one)
4464No Go
4465
4466Gordo | HelloEOS
4467go
4468Deadlock@eosio.sg
4469no go
4470
4471Robin Wen@SuperONE.io
4472Go
4473
4474Dafeng Guo - EOS Asia
4475Go
4476
4477WinLin-EOSBIXIN
4478GO
4479
4480Ben Sigman
4481No Go
4482
4483David P - EOS42
4484No go
4485
4486Emily Bush - shEOS
4487No go
4488Pascal Van Wy | EOS Network by Advanced Blockchain AG
4489No Go
4490Heejae - EOSYS.io
4491GO
4492
4493Guillaume @eostitan.com
4494No go
4495
4496heipacker eosunion
4497go
4498
4499Hubert Chang-EOSeoul.io
4500No go
4501
4502Bohdan CryptoLions 🦁
4503no go
4504
4505Luis Fernando G : EOSMESOdotio 🇬🇹
4506No go
4507
4508Yvonne (EOShenzhen)
4509no go
4510
4511Zhao Yu@ EOSLaoMao.com
4512Yvonne (EOShenzhen)
4513no go
4514duplicate
4515
4516Robrigo - EOS Detroit
4517no go
4518
4519Douglas Horn | EOSAmericas
4520No go
4521phajek eosarmy Patrick
4522no go
4523Robrigo - EOS Detroit invited jesta — Greymass
4524jesta — Greymass
4525go
4526
4527Thomas "Disclaimer" Cox (all opinions mine)
4528END OF VOTING END OF VOTING END OF VOTING
4529
4530Jose Toriello
4531(Eosmeso 1 vote is no go. Sorry for confusion)
4532
4533Mathieu Boulianne - EOS Canada
4534On another note, on the Print / Work Out vote, I got (after cleaning the data): 
4535-55 Print
4536-31 work out
4537
4538jem
4539Appoint ABP, let hiim get ready.
4540
4541Denis | EOS Nation
4542I believe the "no go" is about the RAM disagreement
4543
4544Timothy Lewis
4545There is a lot of deleting going on in this channel
4546
4547Jose Toriello
4548Jose Toriello
4549(Eosmeso 1 vote is no go. Sorry for confusion)
4550Reason was no clarity on print/ram issue
4551
4552Craig Murray - EOS BlockSmith
4553Jose Toriello
4554Reason was no clarity on print/ram issue
4555dan was very clear we should not take the RAM balance
4556Dan said there is only 1 good option, print
4557
4558Sharif Bouktila - EOS Dublinadmin
4559I've deleted some comments in the voting window
4560
4561Sebastian Castro - EOS Argentina 🇦🇷
4562Craig Murray - EOS BlockSmith
4563Dan said there is only 1 good option, print
4564+1
4565
4566Sharif Bouktila - EOS Dublinadmin
4567Only Me , Marc and Eric are admins
4568
4569Robrigo - EOS Detroit
4570My specific reason is waiting to launch with v1.0.2 tag. Would vote GO after tomorrow.
4571
4572Timothy Lewis
4573Robrigo - EOS Detroit
4574My specific reason is waiting to launch with v1.0.2 tag. Would vote GO after tomorrow.
4575Same
4576
4577Jose Toriello
4578Craig Murray - EOS BlockSmith
4579Dan said there is only 1 good option, print
4580I know. But the vote was not counted
4581
4582Craig Murray - EOS BlockSmith
4583why not wait to 1.0.3? or 1.1? or 2.0?
4584no major issues fixed in 1.0.2
4585
4586Robrigo - EOS Detroit
4587Because 1.0.3 is 8 days away, not 1 day away
4588jesta — Greymass
4589You wouldn't even have to upgrade to 1.0.2 immediately.
4590
4591Robrigo - EOS Detroit
4592You asked, I answered :)
4593
4594Timothy Lewis
4595We also will likely get an opinion from Dan on the lost transaction issue.
4596
4597Sherman EOSREAL
4598go
4599
4600Timothy Lewis
4601Get ABP selected
4602
4603Issay@OracleChain
4604Timothy Lewis
4605Same
4606we thought the 3918 issue might be P1, so wait for 1.0.2
4607
4608Timothy Lewis
4609Have them prepare
4610
4611EOS - Antarctica
4612The reasoning for someone’s vote is irrelevant.  We took a vote.  Use the numbers.
4613
4614Thomas "Disclaimer" Cox (all opinions mine)
4615I'm counting 39 GO to 25 NO GO in the telegram channel
4616I can't promise that the data is completely clean
4617
4618Ravi (Blockpro.one)
4619Many BP missing here because not everyone here
4620
4621EOS - Antarctica
4622One does not get to the chance to try and sway opinion after the election.
4623Ben Sigman invited Tal Muskal | LiquidEOS
4624
4625Denis | EOS Nation
4626:-1: 1.0.2 is not a show stopper
4627
4628Jose Toriello
4629Denis | EOS Nation
4630:-1: 1.0.2 is not a show stopper
4631+1
4632
4633Issay@OracleChain
4634but another reason is not all BPs is present here
4635
4636Alexandre Bourget - EOS Canada
4637https://abourget.keybase.pub/votetallysum.txt
4638
4639Jacky - JEDA
4640is 1.0.2 fixes any P0 or P1 issue?
4641
4642Alexandre Bourget - EOS Canada
4643That's my data ^^
4644
4645Nate D - Aloha EOS
4646Jacky - JEDA
4647is 1.0.2 fixes any P0 or P1 issue?
4648No
4649
4650Domi - EOS Rio
4651I'm just concerned with the APB, it wasn't even selected yet, we don't  know what his timezone will be, let him prepare
4652
4653Craig Murray - EOS BlockSmith
4654Jacky - JEDA
4655is 1.0.2 fixes any P0 or P1 issue?
4656no
4657
4658James Sutherland - Cypherglass.com
4659Alexandre Bourget - EOS Canada
4660That's my data ^^
4661:+1:
4662
4663Thomas "Disclaimer" Cox (all opinions mine)
4664The first vote was 52 to 21 //  a 71% YES
4665
4666heipacker eosunion
4667heipacker eosunion
4668go
4669go
4670
4671Jacky - JEDA
4672Craig Murray - EOS BlockSmith
4673no
4674then there is no reason we have to wait for 1.0.2 for my understanding.
4675
4676EOS - Antarctica
4677Why are we taking a vote, if we're not going to put the results into place?
4678
4679Alex - EOS SOCAL
4680Domi - EOS Rio
4681I'm just concerned with the APB, it wasn't even selected yet, we don't know what his timezone will be, let him prepare
4682Agree 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.
4683But also regarding that, the schedule was announced long ago. The abp knew this 12 hour slot was a potential go time.
4684Regardless of timezone
4685
4686Issay@OracleChain
4687[Photo]
4688Thomas "Disclaimer" Cox (all opinions mine) invited EOS Malaysia
4689
4690EOS Malaysia
4691Thanks
4692
4693ndoy |EOS Cafe: Calgary |
4694
4695Issay@OracleChain
4696Photo
4697this might be fake:
4698From deadlock - EOSIO.SG to Everyone:  09:44 PM
4699why celeb has EOSIO.SG website under the name
4700deadlock doesn't know him
4701
4702EOS Malaysia
4703Sorry, there's been some confusion
4704One second
4705
4706Denis | EOS Nation
4707No go's should provide reasons (not blank no go's)
4708
4709EOS - Antarctica
4710Why? A vote is a vote
4711Lee - EOSTEA
4712go
4713
4714Jose Toriello
4715Some 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. 
4716
4717Then we are changing from no go to GO
4718An Byung Chan - EOSYS invited Ashley Gan
4719
4720Denis | EOS Nation
4721Can't update to 1.0.2, code is not released (maybe released)
4722
4723Marek EOSEmerge.io - Poland
4724too bad that it didn't happen today
4725Its a real pitty that they can't make a good reason for no go
4726
4727zhangzc | Onechain
4728+1
4729
4730Denis | EOS Nation
4731How many hours for validation + meshes (12 hours?)
4732
4733jem
4734Marek EOSEmerge.io - Poland
4735Its a real pitty that they can't make a good reason for no go
4736Yes, when you don't like the vote, be sure to challenge the motivation and reason of the opposition. What a great strategy!
4737
4738Daniel Larimer
4739conclusion?
4740
4741jem
4742No conclusion yet, still herding cats.
4743
4744Craig Murray - EOS BlockSmith
4745Daniel Larimer
4746conclusion?
4747too many people are no-go, so it's no go..
4748
4749Daniel Larimer
4750would these be crypto-kitties
4751
4752Rick Schlesinger - EOS New York
4753its a no-go
4754
4755jem
4756Exactly!, Herding crypto kitties!
4757
4758Roman CryptoLions
4759It'll happen next vote.
4760
4761David P - EOS42
4762Yes, I think so next vote
4763Pascal Van Wy | EOS Network by Advanced Blockchain AG invited Pascal | EOS Network by Advanced Blockchain AG
4764
4765Domi - EOS Rio
4766Roman CryptoLions
4767It'll happen next vote.
4768yes, next will be go for sure :relaxed:
4769
4770Rick Schlesinger - EOS New York
4771Roman CryptoLions
4772It'll happen next vote.
4773+1
4774
4775jem
4776Roman CryptoLions
4777It'll happen next vote.
4778I think so.
4779
4780Roman CryptoLions
4781See you all in 9 hrs.
47827 am here.  :blush:
4783
4784Pete BlockMatrix
4785:+1:
4786
4787Lars Ihler - BitSpace
478806 am
4789
4790Igor Lins e Silva - EOS Rio
4791why not use the top_eos_bps_test team on keybase?, the one that Thomas set up for disaster recovery
4792it far more verifiable than telegram
4793
4794jem
4795Igor Lins e Silva - EOS Rio
4796it far more verifiable than telegram
4797:+1:
4798
4799Kyunghwan Kim - EOSeoul.io
4800Igor Lins e Silva - EOS Rio
4801it far more verifiable than telegram
4802+1
4803
4804Craig Murray - EOS BlockSmith
4805that would take a lot of time to onboard all those people, especially asian groups
4806
4807Igor Lins e Silva - EOS Rio
4808most of the bps already have keybase setup
4809Dafeng Guo - EOS Asia invited Edward Lew - EOS Land
4810
4811Craig Murray - EOS BlockSmith
4812"most"? based on what metric?
4813Dafeng Guo - EOS Asia invited Goh MEET.ONE
4814
4815Ricardo Marlière - EOS Brazil
4816Igor Lins e Silva - EOS Rio
4817most of the bps already have keybase setup
4818keybase +1
4819
4820Igor Lins e Silva - EOS Rio
4821based on 207 members we validated in the ghostbusters team
4822we can select one vote per BP official website with dns proof on keybase
4823
4824Craig Murray - EOS BlockSmith
4825if that's what everyone wants and you can get consensus
4826thomas is right now telling us how he thinks we are going to do it next meeting
4827
4828ndoy |EOS Cafe: Calgary |
4829Igor Lins e Silva - EOS Rio
4830based on 207 members we validated in the ghostbusters team
4831yes for keybase, no need to reinvent the wheel. We have validated BPs there, just to make sure no duplicate e.g. between me and Syed
4832
4833Igor Lins e Silva - EOS Rio
4834it was just a suggestion ;)
4835
4836Craig Murray - EOS BlockSmith
4837Igor Lins e Silva - EOS Rio
4838it was just a suggestion ;)
4839:+1:
4840
4841Douglas Horn | EOSAmericas
4842Keybase is a good suggestion.
4843
4844crazybit@SuperONE.io
4845https://eos.live/detail/2500  looks like this is EOS crypto-kitties called Pandafun :grin:
4846eos.live
4847EOS LIVE - 发现 EOS 最热门产品及最新优质资讯
4848发现 EOS 最热门产品及最新优质资讯，EOS LIVE 将及时为你呈现时下 EOS 社区最热门产品及最新优质资讯 。这里是 EOSer 发现和分享 EOS 社区最新 Dapp 项目、区块见证人、以及 EOS 社区线下活动和最新优质资讯的产品与资讯聚合平台。
4849
4850Igor Lins e Silva - EOS Rio
4851and is super easy for people to cast the vote on their public folders
4852
4853ndoy |EOS Cafe: Calgary |
4854David says we'll use zoom poll
4855
4856Igor Lins e Silva - EOS Rio
4857but can that prevent multiple votes per bp?
4858
4859ndoy |EOS Cafe: Calgary |
4860I never use zoom poll, so I'm not sure how it gets counted
4861unless with invite meeting maybe, using our email
4862
4863Thomas "Disclaimer" Cox (all opinions mine)
4864I want to see only one person attending PER BP
4865
4866Douglas Horn | EOSAmericas
4867Short of any unknown issue, EOSAmericas will be changing our vote to “Go” in the next vote. We will examine issue #3918 in the interim.
4868Sherman EOSREAL invited Felicia EOSREAL
4869
4870Domi - EOS Rio
4871@thomasbcox we can use keybase, just a suggestion :)
4872
4873ndoy |EOS Cafe: Calgary |
4874lots of people in the zoom chat I never talk to them in any testnets channel. I'm not saying that they are not BP candidates but we do need to verify who casts vote
4875
4876Ben Sigman
4877https://status.producer.vote/
4878
4879EOS Mainnet Status
4880This site shows the daily report from the EOS launch.
4881
4882Marek EOSEmerge.io - Poland
4883Then keybase is a good option
4884
4885Denis | EOS Nation
4886If "print" is decided, we still have "no go" votes for that reason (we need to include arguments for "no" votes to filter out some votes)
4887Edward Lew - EOS Land
4888Awesome! Thanks all of your hard working
4889
4890James Sutherland - Cypherglass.com
4891@thomasbcox @marcantoineross @sharifbouktila  — Please can I add to the agenda for the next meeting; Permission to stream these meetings publicly.