SHARE
TWEET

Untitled

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