API tools faq
paste
Advertisement
Guest User

Untitled

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