API tools faq
paste
Guest User

Untitled

a guest
Jun 7th, 2018
203
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 485.95 KB | None | 0 0
raw download clone embed print report
  1. Your Telegram History in "EOS Validation (EMLG)"
  2.  
  3. .....28.05.2018 03:18:24, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>upgraded the group to a supergroup<<
  4. 28.05.2018 03:20:38, Sharif Bouktila - EOS Dublin [@sharifbouktila]: This purpose of this Group is to agree how we validate EOS Mainnet.
  5.  
  6. Once we have agreed, we will look for BPs to issue a statement to state that they are in agreement.
  7. .....28.05.2018 03:23:07, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>changed group photo<<
  8. 28.05.2018 03:27:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: For now if you can please share this group with BPs who we know will be positive.
  9.  
  10. and
  11.  
  12. If you can post here what is the Minimum which is needed for an EOS Chain to be validated as Mainnet
  13.  
  14. I will compile into a Draft Document and then host a call to try reach agreement.
  15. 28.05.2018 03:29:01, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Lets aim to have the Conference call tomorrow and Agreement Statement issued by all BPs on May 30th.
  16. 28.05.2018 03:29:17, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Does that sound achievable?
  17. 28.05.2018 03:29:21, Eric - sw/eden [@xebb82]: Sounds good to me.
  18. 28.05.2018 03:29:42, Sam - EOS Dublin [@samnoble]: 👍
  19. 28.05.2018 03:30:02, Igor Lins e Silva - EOS Rio [@igorls]: Agreed
  20. .....28.05.2018 03:30:51, jem [@jemxpat]: >>unsupported service message type: messageActionChatJoinedByLink<<
  21. 28.05.2018 03:31:30, jem [@jemxpat]: Yup
  22. .....28.05.2018 03:39:34, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>changed group name to "EOS Validation (TEMP Group)"<<
  23. .....28.05.2018 03:45:32, Marcin @eosgreen.io [@marcin_eosgreen]: >>unsupported service message type: messageActionChatJoinedByLink<<
  24. 28.05.2018 03:47:14, Marcin @eosgreen.io [@marcin_eosgreen]: Hi Guys!
  25. 28.05.2018 03:48:26, Marcin @eosgreen.io [@marcin_eosgreen]: what time are you planing to have this call?
  26. 28.05.2018 03:49:48, Eric - sw/eden [@xebb82]: What do we have to agree upon to do a successful launch?
  27.  
  28. Validation
  29. * ERC20 distribution (already agreed)
  30. * Extra accounts and contracts? (eosio.disco for example)
  31. * Also <producer-name>.p accounts (?)
  32. * Can we agree that all of us will burn 0.1 EOS or something for those accounts?
  33. * How do we pay for ram?
  34. * Early created account will pay more for same amount of ram than last created account
  35. * Extra producer accounts (EOS.Dublin.p)? Other name standard?.
  36. * Is it ok to use multisig in future to create more accounts for newly registered producers?
  37. * How do we want to (s)elect eosio?
  38. * How do we want to (s)elect ABPs?
  39. *
  40.  
  41. I'll update this message as we come up with more things.
  42. 28.05.2018 03:51:12, Sharif Bouktila - EOS Dublin [@sharifbouktila]: 21:00 UTC Y/N ?
  43. .....28.05.2018 03:53:06, Basit Raza - EOSVibes [@boltxyz]: >>unsupported service message type: messageActionChatJoinedByLink<<
  44. .....28.05.2018 03:54:30, Kyle - EOSVibes [@TheAwakenment]: >>unsupported service message type: messageActionChatJoinedByLink<<
  45. .....28.05.2018 03:56:38, Sukesh Tedla (EOSGreen) [@Sukeshtedla]: >>unsupported service message type: messageActionChatJoinedByLink<<
  46. 28.05.2018 03:57:54, Eric - sw/eden [@xebb82]: Evening time in US means night time in asia, right? Better to run 09:00 UTC - or am I missing something?
  47. 28.05.2018 03:59:31, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Photo]]
  48. 28.05.2018 03:59:47, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Basically add 12 hours to this on 30th May.
  49. .....28.05.2018 04:00:45, Devin Lee KOREOS.IO [@indend007]: >>unsupported service message type: messageActionChatJoinedByLink<<
  50. .....28.05.2018 04:08:13, Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer [@tyeenoprom]: >>unsupported service message type: messageActionChatJoinedByLink<<
  51. .....28.05.2018 04:10:36, Khosi Morafo eosAfrica [@khosimorafo]: >>unsupported service message type: messageActionChatJoinedByLink<<
  52. .....28.05.2018 04:14:39, An Byung Chan - EOSYS [@Anbyungchan]: >>unsupported service message type: messageActionChatJoinedByLink<<
  53. 28.05.2018 04:15:01, Khosi Morafo eosAfrica [@khosimorafo]: Hi Guys, does the conference call mean a freeze on the discussion? I hope not. Erics list seems rather large and trying to fit that into a call could be difficult.
  54. .....28.05.2018 04:17:41, Robin [email protected] [@robinwen]: >>unsupported service message type: messageActionChatJoinedByLink<<
  55. 28.05.2018 04:18:32, Eric - sw/eden [@xebb82]: I think we'll need to increase the list further. And I'm open for doing several calls with different people multiple times during the coming hours if anyone thinks they can benefit from that.
  56. .....28.05.2018 04:19:54, Ross (EOSphere) [@rossco99]: >>unsupported service message type: messageActionChatJoinedByLink<<
  57. 28.05.2018 04:20:23, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Do as many calls as is needed , but we have a hard deadline this weekend.
  58. 28.05.2018 04:22:56, Eric - sw/eden [@xebb82]: Can we make it into a super group so I can link to my message above?
  59. 28.05.2018 04:23:05, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Try to get to a point that we have a checklist and once all items are complete you will be happy to publicly state you are happy to call that chain EOS Mainnet
  60.  
  61. Once we have that we should try agree how many others need to also agree.
  62. 28.05.2018 04:24:05, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I’ve made you an admin.
  63. 28.05.2018 04:24:48, Khosi Morafo eosAfrica [@khosimorafo]: [[Webpage]]For those who may want to add the list, here is a doc: -
  64. https://docs.google.com/document/d/1HG40PwrN0fL62TfwbOrrCjUpoQqlVhGtQb7WJe7kulA/edit?usp=sharing
  65.  
  66. Based on Eric's original list
  67. 28.05.2018 04:26:16, Eric - sw/eden [@xebb82]: I can't seem to make it super.
  68. .....28.05.2018 04:27:36, Ravi (Blockpro.one) [@ravincal]: >>unsupported service message type: messageActionChatJoinedByLink<<
  69. 28.05.2018 04:28:01, Eric - sw/eden [@xebb82]: nice, that's better
  70. .....28.05.2018 04:50:19, Vahid Toosi - sw/eden [@vahidtoosi1]: >>unsupported service message type: messageActionChatJoinedByLink<<
  71. .....28.05.2018 04:52:51, mao EOSREAL [@maoyifeng]: >>unsupported service message type: messageActionChatJoinedByLink<<
  72. .....28.05.2018 04:53:58, Lee - EOSTEA [@strahe]: >>unsupported service message type: messageActionChatJoinedByLink<<
  73. 28.05.2018 04:55:31, mao EOSREAL [@maoyifeng]: hi bro and sis. It is a urgent and necessary task to do. Glad you cover it!
  74. .....28.05.2018 04:56:27, Ian(Yahuang Wu) - MEET.ONE [@wuyahuang]: >>unsupported service message type: messageActionChatJoinedByLink<<
  75. .....28.05.2018 05:06:49, Dafeng Guo - EOS Asia [@dftle]: >>unsupported service message type: messageActionChatJoinedByLink<<
  76. .....28.05.2018 05:07:01, Dafeng Guo - EOS Asia [@dftle]: >>unsupported service message type: messageActionChatAddUsers<<
  77. 28.05.2018 05:07:22, aza eosar [@p17er0bl3do]: about pausing the chain / altering base contracts i believe we should avoid that, we can validate the state of the chain at some specific block, even though it will be a little harder
  78. .....28.05.2018 05:08:07, Tim Weston - GenerEOS (BP Sydney) [@timweston]: >>unsupported service message type: messageActionChatJoinedByLink<<
  79. 28.05.2018 05:08:12, Sharif Bouktila - EOS Dublin [@sharifbouktila]: How would we agree on what block ?
  80. 28.05.2018 05:08:27, Dafeng Guo - EOS Asia [@dftle]: Then I think that’s 3 am beijing time
  81. .....28.05.2018 05:09:09, Dafeng Guo - EOS Asia [@dftle]: >>invited Alexandre Bourget - EOS Canada [@abourget]<<
  82. 28.05.2018 05:10:02, aza eosar [@p17er0bl3do]: after all system contracts have been set and stake holders account have been created, basically once the boot finishes
  83. .....28.05.2018 05:10:06, Charles H - EOS 42 [@ankh2054]: >>unsupported service message type: messageActionChatJoinedByLink<<
  84. 28.05.2018 05:10:17, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Would you prefer earlier or later? Or is that workable ?
  85. 28.05.2018 05:11:02, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Can you add the Google Doc
  86. 28.05.2018 05:13:07, aza eosar [@p17er0bl3do]: will see where it fits
  87. .....28.05.2018 05:13:10, Bean@EOS Cannon [@Luckybean]: >>unsupported service message type: messageActionChatJoinedByLink<<
  88. 28.05.2018 05:16:14, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Maybe add it as an open question “can we agree a specific block upon which to validate?”
  89. 28.05.2018 05:18:26, Charles H - EOS 42 [@ankh2054]: 09:00 UTC?
  90. 28.05.2018 05:20:02, Sharif Bouktila - EOS Dublin [@sharifbouktila]: One question in the Doc is about the launch process , let’s keep this discussion agnostic to the approach and aim for a checklist which can be used regardless.
  91.  
  92. Think , could Deloitte (or similar) pick up and use this to independently validate
  93. 28.05.2018 05:20:14, Sharif Bouktila - EOS Dublin [@sharifbouktila]: 21:00 UTC
  94. 28.05.2018 05:21:17, Charles H - EOS 42 [@ankh2054]: Okay cool thanks
  95. 28.05.2018 05:22:36, Eric - sw/eden [@xebb82]: +1
  96. I added about Alexs yaml file,because it's the easiest way to understand the launch process right now.
  97. .....28.05.2018 05:23:50, Lucas @EOS Beijing [@LucasEosBeijing]: >>unsupported service message type: messageActionChatJoinedByLink<<
  98. .....28.05.2018 05:30:06, Jorge Ferrando - EOSMetal [@jorfermo]: >>unsupported service message type: messageActionChatJoinedByLink<<
  99. .....28.05.2018 05:30:48, LOME eosfans [@lomect]: >>unsupported service message type: messageActionChatJoinedByLink<<
  100. .....28.05.2018 05:31:05, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>unsupported service message type: messageActionPinMessage<<
  101. 28.05.2018 05:32:53, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I’ve pinned the Google Document
  102.  
  103. Please read and add any questions / requirements you feel need to be included in our EOS Validation Test Plan
  104. 28.05.2018 05:33:16, aza eosar [@p17er0bl3do]: Added, would be the same block at which we would "pause" it
  105. .....28.05.2018 05:39:12, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: >>unsupported service message type: messageActionChatJoinedByLink<<
  106. 28.05.2018 05:42:12, Dafeng Guo - EOS Asia [@dftle]: Considering the large number of BPs in Asia, I propose 13:00 UTC.
  107. .....28.05.2018 05:43:10, Larry Ma @EOS CANNON [@larrymanysh]: >>unsupported service message type: messageActionChatJoinedByLink<<
  108. 28.05.2018 05:44:05, mao EOSREAL [@maoyifeng]: Please just let us know whatever time it would be. I will stay for the rest of the month...
  109. 28.05.2018 05:45:40, Eric - sw/eden [@xebb82]: Stated before, stating again;
  110. Several meeting during all of today could allow us to come to consensus quicker.
  111. 28.05.2018 05:46:25, Dafeng Guo - EOS Asia [@dftle]: Agree
  112. 28.05.2018 05:46:51, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Agreed - but let’s try make sure we have good participation and a circulation of minutes from each call.
  113. 28.05.2018 05:47:55, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Maybe have a minimum of 5 teams on each call?
  114. 28.05.2018 05:49:09, Sharif Bouktila - EOS Dublin [@sharifbouktila]: And on each one agree who will document actions / decisions and publish them
  115. .....28.05.2018 06:07:30, Michael Yeates [@michaelyeates]: >>unsupported service message type: messageActionChatJoinedByLink<<
  116. 28.05.2018 06:09:17, Eric - sw/eden [@xebb82]: We could log calls as comments on each point to discuss to make it as simple to follow as possible.
  117. I won't read any of the minutes and I reckon most of us don't have time tondo that anyways.
  118. .....28.05.2018 06:09:18, Kevin Rose - EOS New York [@eosnewyork]: >>unsupported service message type: messageActionChatJoinedByLink<<
  119. 28.05.2018 06:09:44, Kevin Rose - EOS New York [@eosnewyork]: Hey everyone
  120. .....28.05.2018 06:09:56, Kevin Rose - EOS New York [@eosnewyork]: >>unsupported service message type: messageActionChatAddUsers<<
  121. .....28.05.2018 06:10:54, Kevin Rose - EOS New York [@eosnewyork]: >>invited Warrick FitzGerald - EOS New York [@WarrickF]<<
  122. .....28.05.2018 06:15:14, Matthew Bryce 马修·布赖斯 - BitSpace [@matthewbryce]: >>unsupported service message type: messageActionChatJoinedByLink<<
  123. .....28.05.2018 06:17:10, Cryptosufi - 威杰 - BitSpace [@KryptoSufi]: >>unsupported service message type: messageActionChatJoinedByLink<<
  124. 28.05.2018 06:18:53, Eric - sw/eden [@xebb82]: Feel free to hit me up for a vc at any time if anyone needs explanations or clarifications regarding anything in the document.
  125. .....28.05.2018 06:20:41, Orchid K - EOSYS [@appletreehill]: >>unsupported service message type: messageActionChatJoinedByLink<<
  126. .....28.05.2018 06:25:54, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: >>unsupported service message type: messageActionChatJoinedByLink<<
  127. 28.05.2018 06:25:58, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: Hello all
  128. .....28.05.2018 06:28:01, David P - EOS42 [@GunnisonCap]: >>unsupported service message type: messageActionChatJoinedByLink<<
  129. 28.05.2018 06:36:03, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Hi All
  130.  
  131. I’ve pinned the Google Document
  132.  
  133. Please read and add any questions / requirements you feel need to be included in our EOS Validation Test Plan
  134.  
  135. The end goal here is an agreement on how a chain should be validated as mainnet.
  136.  
  137. Once the agreed Validation is complete each team should be comfortable to publicly declare the EOS Mainnet.
  138. .....28.05.2018 06:36:07, Jae Chung - HKEOS [@jaechung]: >>unsupported service message type: messageActionChatJoinedByLink<<
  139. 28.05.2018 06:41:22, Kyle - EOSVibes [@TheAwakenment]: Glad we’re doing this.
  140. Agreeing and declaring the process is equally as important as agreeing to the intent of launching one main net.
  141. .....28.05.2018 06:42:50, Roman CryptoLions [@romanskaskiw]: >>unsupported service message type: messageActionChatJoinedByLink<<
  142. 28.05.2018 06:55:30, Nathan Rempel | GenerEOS Sydney [@nsrempel]: whats the best way to add to the document so it doesn't get messy?
  143. 28.05.2018 06:55:33, David P - EOS42 [@GunnisonCap]: Fine by me
  144. 28.05.2018 06:56:37, David P - EOS42 [@GunnisonCap]: Middle of the night in Asia isn’t it, actually two calls would work best for global coverage
  145. 28.05.2018 06:57:01, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Ok guys I just want to check in here
  146. 28.05.2018 06:57:32, Michael Yeates [@michaelyeates]: i think adding comments is the best way and then the owner can modify the doc
  147. 28.05.2018 06:57:32, Eric - sw/eden [@xebb82]: I'm trying to keep an eye on it and will try to help us clean it.
  148. 28.05.2018 06:57:44, Eric - sw/eden [@xebb82]: +1
  149. 28.05.2018 06:57:46, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Everyone is aware that blocks are produced for free, forever, until 15% token supply is staked
  150. 28.05.2018 06:57:54, Nathan Rempel | GenerEOS Sydney [@nsrempel]: but blocks are being produced
  151. 28.05.2018 06:58:22, Eric - sw/eden [@xebb82]: yes
  152. 28.05.2018 06:58:30, Charles H - EOS 42 [@ankh2054]: Yes I believe so and the 21 BPs booting the chain cannot be changed either.
  153. 28.05.2018 06:58:36, Eric - sw/eden [@xebb82]: true
  154. 28.05.2018 06:58:53, Michael Yeates [@michaelyeates]: i think safest it to boot and then freeze for validation
  155. 28.05.2018 06:59:01, Nathan Rempel | GenerEOS Sydney [@nsrempel]: ok great, ive seen some misinformation around where somehow blocks wouldn't be produced at all heh
  156. 28.05.2018 06:59:07, Michael Yeates [@michaelyeates]: we need the producers to stick around to unfreeze
  157. 28.05.2018 06:59:23, Eric - sw/eden [@xebb82]: we are discussing freezing the chain as a validation step
  158. 28.05.2018 06:59:44, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: I think I know how to freeze chain
  159. 28.05.2018 06:59:49, Eric - sw/eden [@xebb82]: =)
  160. 28.05.2018 06:59:52, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: but didnt tested yet
  161. 28.05.2018 07:00:02, Eric - sw/eden [@xebb82]: We've tested quite a bit, so that's no problem.
  162. 28.05.2018 07:00:10, Igor Lins e Silva - EOS Rio [@igorls]: can't we just call /producer/pause ?
  163. 28.05.2018 07:00:13, Eric - sw/eden [@xebb82]: yes
  164. 28.05.2018 07:00:15, Charles H - EOS 42 [@ankh2054]: So we freeze and then validate, then unfreeze and allow votes.
  165. 28.05.2018 07:00:27, Igor Lins e Silva - EOS Rio [@igorls]: yes sir
  166. 28.05.2018 07:00:40, Eric - sw/eden [@xebb82]: That's one way of doing it that I could absolutely agree on.
  167. 28.05.2018 07:01:01, Charles H - EOS 42 [@ankh2054]: So we need to call producer pause on all or only one?
  168. 28.05.2018 07:01:06, Eric - sw/eden [@xebb82]: yes
  169. 28.05.2018 07:01:08, Eric - sw/eden [@xebb82]: all
  170. 28.05.2018 07:01:11, Michael Yeates [@michaelyeates]: +1
  171. 28.05.2018 07:01:18, Eric - sw/eden [@xebb82]: You control your own node via that api
  172. 28.05.2018 07:01:35, Michael Yeates [@michaelyeates]: or depending on firewall, other peoples nodes
  173. 28.05.2018 07:01:36, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: why we need to freeze?
  174. 28.05.2018 07:01:37, Eric - sw/eden [@xebb82]: We can jump on a call if u want more info Charles. Welcome back btw.
  175. 28.05.2018 07:01:44, Eric - sw/eden [@xebb82]: Validate state.
  176. 28.05.2018 07:01:47, Charles H - EOS 42 [@ankh2054]: Thanks :)
  177. 28.05.2018 07:01:53, Michael Yeates [@michaelyeates]: to prevent tokens moving while we validate
  178. 28.05.2018 07:02:04, Igor Lins e Silva - EOS Rio [@igorls]: 🙊
  179. 28.05.2018 07:02:10, Nathan Rempel | GenerEOS Sydney [@nsrempel]: @BohdanCryptoLions you have experience generating blocksnapshots, can you specify which block to produce the snapshot against
  180. 28.05.2018 07:03:02, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: but I think we can validate till when eosio resign .
  181. 28.05.2018 07:03:46, Kevin Rose - EOS New York [@eosnewyork]: Can our goal also be how to choose one from multiple valid and correct chains to be called the EOS mainnet?
  182. 28.05.2018 07:04:11, Eric - sw/eden [@xebb82]: Not if some of us wants to be able to say loop all existing accounts, and check balance and compare with file.
  183. 28.05.2018 07:05:00, Michael Yeates [@michaelyeates]: if people start transacting and then we have a problem with validation, we would have to create another chain and all those transactions would be reversed
  184. 28.05.2018 07:05:06, Roman CryptoLions [@romanskaskiw]: ❤️
  185. 28.05.2018 07:05:54, Charles H - EOS 42 [@ankh2054]: Yes and I wonder how we do this. Assuming somewhere else in the world they are discussing this right now too. How too boot and validate a chain.
  186. 28.05.2018 07:06:07, Nathan Rempel | GenerEOS Sydney [@nsrempel]: (Especially in China....)
  187. 28.05.2018 07:06:43, Charles H - EOS 42 [@ankh2054]: Does block.one have any official capacity to choose?
  188. 28.05.2018 07:06:57, Eric - sw/eden [@xebb82]: Been in contact with some of the BPCs from China. Some have joined in here already, other I rely messages to in private.
  189. 28.05.2018 07:06:58, Kevin Rose - EOS New York [@eosnewyork]: No
  190. 28.05.2018 07:07:25, Kevin Rose - EOS New York [@eosnewyork]: Chinese Block Producers are on the same page. We want one mainnet.
  191. 28.05.2018 07:07:31, Eric - sw/eden [@xebb82]: +1
  192. 28.05.2018 07:08:07, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I appreciate that, but there may be some doing other boot tests?
  193. 28.05.2018 07:08:16, Kevin Rose - EOS New York [@eosnewyork]: [[Webpage]]As a thought starter, here is a proposal on how to randomly pick a chain. Feel free to tear it apart. https://docs.google.com/document/d/1Ya2l-Yimc1meyOBoSpE0QWX8ITaAYUwKvBMpRT-rInQ/edit?usp=sharing
  194. 28.05.2018 07:08:27, Eric - sw/eden [@xebb82]: I hope so. I hope most of us are / have been. Both publicly and in private.
  195. 28.05.2018 07:09:32, Kevin Rose - EOS New York [@eosnewyork]: Not perfect, not even final. Just a draft of thoughts.
  196. 28.05.2018 07:10:16, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: my thoughts are that we need to validate all chain from start until eosio user chnage rights to multisig (eosio.prods). after that boot is finished and changes to system can be done only by 2/3 producers. So you just would like just pause chaine for validation after eosio resign, am I right?
  197. 28.05.2018 07:11:27, Eric - sw/eden [@xebb82]: Yes, that's the plan. Well, atleast the proposition.
  198. 28.05.2018 07:11:32, David P - EOS42 [@GunnisonCap]: Fully agree with this
  199. 28.05.2018 07:12:31, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: I think its ok.
  200. 28.05.2018 07:13:06, Nathan Rempel | GenerEOS Sydney [@nsrempel]: How do you prevent third party transactions in the interim between network start and the freeze? The moment the system, bios, token transactions and snapshot are loaded third parties could publish transactions
  201. 28.05.2018 07:13:09, Eric - sw/eden [@xebb82]: 👍
  202. 28.05.2018 07:13:18, Nathan Rempel | GenerEOS Sydney [@nsrempel]: contracts*
  203. 28.05.2018 07:13:34, Eric - sw/eden [@xebb82]: We might need to start the chain with only eosio+abps connected from start.
  204. 28.05.2018 07:13:43, Eric - sw/eden [@xebb82]: Until freeze is active.
  205. 28.05.2018 07:14:29, David P - EOS42 [@GunnisonCap]: However this works, random section is the only way to do this - assuming multiple, identical term bios chains. That way there cannot become arguments between BPs regarding the kudos of being part of a launch 21. That will happen without this being randomised.
  206. 28.05.2018 07:14:47, Michael Yeates [@michaelyeates]: can we set it all up with only specified peers
  207. 28.05.2018 07:14:55, Michael Yeates [@michaelyeates]: should keep unwanted nodes out
  208. .....28.05.2018 07:26:05, Chitty 🅑 - EOS Argentina [@JChitty]: >>unsupported service message type: messageActionChatJoinedByLink<<
  209. 28.05.2018 07:26:37, Nathan Rempel | GenerEOS Sydney [@nsrempel]: hmm, if all producers in a boot process block the http server and delay launching "public exposed nodes" it should work... as long as the nominated producers actually follow those guidelines
  210. 28.05.2018 07:27:19, Eric - sw/eden [@xebb82]: absolutely
  211. 28.05.2018 07:27:58, Eric - sw/eden [@xebb82]: +1 :)
  212. 28.05.2018 07:28:21, Igor Lins e Silva - EOS Rio [@igorls]: works.. but its a very uncontrollabe solution
  213. 28.05.2018 07:28:52, Nathan Rempel | GenerEOS Sydney [@nsrempel]: yeah, most things in the document require 21 people to all follow the rules
  214. 28.05.2018 07:29:31, Eric - sw/eden [@xebb82]: At this point it's not dangerous though.
  215. We throw away the chain and restart if someone fucks up.
  216. 28.05.2018 07:29:47, Eric - sw/eden [@xebb82]: The danger starts coming when people have started voting. Which is why I like this solution.
  217. .....28.05.2018 07:29:48, CLains - BitSpace [@CLains]: >>unsupported service message type: messageActionChatJoinedByLink<<
  218. 28.05.2018 07:29:58, Eric - sw/eden [@xebb82]: If we loose peoples votes - that's bad PR.
  219. 28.05.2018 07:33:53, Nathan Rempel | GenerEOS Sydney [@nsrempel]: can we easily confirm via log that all transactions taking place have been legitimate by the boot node and also have been the only transactions? I'm assuming the transaction log you could easily spot if an unspecified account or a rogue boot producer intiated a transfer/etc
  220. 28.05.2018 07:36:22, Michael Yeates [@michaelyeates]: the transfer would have gone somewhere, so genesis balances would not validate and the chain would be tossed
  221. 28.05.2018 07:36:23, Eric - sw/eden [@xebb82]: We have a few different ideas for validation scripts.
  222. In eos-bios Alex validates each and every transaction bit-by-bit.
  223. Igor has a quite advanced script building up a database.
  224. An I'm planning to; loop all accounts, validate against ERC20 and make sure their code = 000000000. Loop ERC20 - validate against accounts. Validate contract hashes, and so forth.
  225. 28.05.2018 07:36:41, Michael Yeates [@michaelyeates]: the more methods for validation the better
  226. 28.05.2018 07:36:49, Eric - sw/eden [@xebb82]: +1
  227. 28.05.2018 07:36:55, Michael Yeates [@michaelyeates]: we all agree on final state so they should all match
  228. 28.05.2018 07:37:03, Eric - sw/eden [@xebb82]: Then we have the human layer if indeed something doesn't validate.
  229. 28.05.2018 07:37:34, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: +++
  230. 28.05.2018 07:37:37, Michael Yeates [@michaelyeates]: [[GIF, size 81'601 bytes]]
  231. 28.05.2018 07:38:24, Nathan Rempel | GenerEOS Sydney [@nsrempel]: alright cool, im happy to keep the chain private until validation, makes the most sense
  232. 28.05.2018 07:39:00, Nathan Rempel | GenerEOS Sydney [@nsrempel]: impetus would exist to validate as rapidly as possible and go public as early as possible to be "first to market"
  233. 28.05.2018 07:39:24, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: anyone did some validation tests, how long can it last?
  234. 28.05.2018 07:40:33, Eric - sw/eden [@xebb82]: Ping @igorls
  235. 28.05.2018 07:41:30, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Is the 3 Eric lists sufficient?
  236.  
  237. If so then no need for “more” as part of the agreed validation plan.
  238.  
  239. Let’s try name those approaches so they aren’t “Alex’s , Eric’s” etc...
  240. 28.05.2018 07:42:14, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Cycle 1 , Cycle 2 , Cycle 3
  241. 28.05.2018 07:42:58, Sharif Bouktila - EOS Dublin [@sharifbouktila]: And define what the approach is and how they are executed
  242. 28.05.2018 07:43:33, Michael Yeates [@michaelyeates]: we would have our own method, but im sure independent people will write their own
  243. 28.05.2018 07:44:34, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Sure but as the end goal here we want one agreed approach that once passed everyone is confident declaring a Mainnet
  244. 28.05.2018 07:46:06, Eric - sw/eden [@xebb82]: We have one more from @winlineosbixin
  245. 28.05.2018 07:46:34, Eric - sw/eden [@xebb82]: We also need to try to get more people to generate the snapshots probably, because.. maybe that tool can't be trusted? 🤷🏻‍♂️
  246. 28.05.2018 07:46:44, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Cool , cycle 4 ...
  247. 28.05.2018 07:46:51, Sharif Bouktila - EOS Dublin [@sharifbouktila]: +1
  248. 28.05.2018 07:48:46, Eric - sw/eden [@xebb82]: The plan with my validation isn't really first and foremost to do everything, or even to do everything as quick as possible.
  249. The plan is to make it as easy to read as possible with as few dependencies as possible. So anyone with a linux machine who has compiled the latest version can run it.
  250. 28.05.2018 07:48:52, Eric - sw/eden [@xebb82]: I will also be running at least Igors tool.
  251. 28.05.2018 07:50:43, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Try to think about what tests you would be comfortable for someone else to run and confirm back.
  252. 28.05.2018 07:51:13, Eric - sw/eden [@xebb82]: Sure thing.
  253. I'll be away for an hour trying to get some shut eye so I can be alive on interview tonight.
  254. .....28.05.2018 07:53:13, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionChatJoinedByLink<<
  255. 28.05.2018 07:55:27, Alexandre Bourget - EOS Canada [@abourget]: Yes, that'd be the end block for freeze.
  256. 28.05.2018 07:55:36, Michael Yeates [@michaelyeates]: I would say that any chain passing validation should be declared a Mainnet candidate
  257. 28.05.2018 07:56:43, Alexandre Bourget - EOS Canada [@abourget]: WinLin also wrote a validation script, taking into account what people have in eosio.stake
  258. 28.05.2018 07:56:48, Alexandre Bourget - EOS Canada [@abourget]: Is he here ?
  259. 28.05.2018 07:56:58, Michael Yeates [@michaelyeates]: The most important goal is to make the token holders confident that the chain represents the snapshot and that nobody has any special rights or code
  260. 28.05.2018 07:57:50, Michael Yeates [@michaelyeates]: Multiple independent scripts all confirming that is the gold standard
  261. 28.05.2018 07:59:43, Alexandre Bourget - EOS Canada [@abourget]: I have a program that can filter the p2p protocol, do deep packet or transaction inspection and could stop propagation of blocks after a given action (eosio::updateauth aka eosio resignation)
  262. 28.05.2018 08:00:07, Alexandre Bourget - EOS Canada [@abourget]: People could use it to do validation
  263. 28.05.2018 08:00:26, Michael Yeates [@michaelyeates]: We can pause production
  264. 28.05.2018 08:00:33, Alexandre Bourget - EOS Canada [@abourget]: That won't work
  265. 28.05.2018 08:01:06, Alexandre Bourget - EOS Canada [@abourget]: Unless you manage to tell everyone to stop their production at the same time. You only need one transaction in a block post-resignation for the process to fail.
  266. 28.05.2018 08:01:34, Alexandre Bourget - EOS Canada [@abourget]: Pausing production is only instructing your node to not produce when it's on schedule
  267. 28.05.2018 08:01:39, Michael Yeates [@michaelyeates]: You can do that on a closed network, then open for validation
  268. 28.05.2018 08:02:36, Alexandre Bourget - EOS Canada [@abourget]: The moment it is "open for validation", it is also open for transactions.
  269. 28.05.2018 08:03:00, Michael Yeates [@michaelyeates]: If a chain allows any transactions then it fails validation
  270. 28.05.2018 08:03:13, Michael Yeates [@michaelyeates]: How about we add that to the validation script?
  271. .....28.05.2018 08:07:43, Boy Maas - EOS Amsterdam [@monetashi]: >>unsupported service message type: messageActionChatJoinedByLink<<
  272. 28.05.2018 08:07:56, Sharif Bouktila - EOS Dublin [@sharifbouktila]: First past the post ?
  273. 28.05.2018 08:08:03, WinLin-EOSBIXIN [@hiwinlin]: [[Photo]]
  274. 28.05.2018 08:08:27, WinLin-EOSBIXIN [@hiwinlin]: eos_onchain_validator.py just test the 1000 account onchain validation
  275. 28.05.2018 08:08:54, WinLin-EOSBIXIN [@hiwinlin]: the speed is 851 accounts/sec for single node
  276. 28.05.2018 08:09:07, Michael Yeates [@michaelyeates]: validation is going to take a couple of days i think
  277. 28.05.2018 08:09:45, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I don’t see any need to rush.
  278. 28.05.2018 08:10:07, Michael Yeates [@michaelyeates]: not at all
  279. 28.05.2018 08:10:19, Michael Yeates [@michaelyeates]: i would like at least 2 weeks for validation and testing
  280. 28.05.2018 08:10:42, WinLin-EOSBIXIN [@hiwinlin]: @abourget I test the eos-bios boot --single with the eos_validator_tools.py
  281. 28.05.2018 08:10:50, Michael Yeates [@michaelyeates]: if we lose 7 producers before the chain is opened then it is dead and we have to start again
  282. 28.05.2018 08:11:51, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: setprods now is in system contract, so probably will work even with eosio as multisig
  283. 28.05.2018 08:13:08, Michael Yeates [@michaelyeates]: the setprods wouldnt be irreversible though?
  284. 28.05.2018 08:13:18, Alexandre Bourget - EOS Canada [@abourget]: Is it ?? It wasn't when I checked... I submitted a PR to add it and it was refused.
  285. 28.05.2018 08:13:44, Michael Yeates [@michaelyeates]: [[Webpage]]https://github.com/EOSIO/eos/blob/master/contracts/eosio.system/eosio.system.abi#L490
  286. 28.05.2018 08:14:06, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: hehe you were faster
  287. 28.05.2018 08:14:14, Alexandre Bourget - EOS Canada [@abourget]: It's on the ABI so it doesn't break if you fetch blocks where eosio.bios was present. It's not in the code
  288. 28.05.2018 08:14:33, Alexandre Bourget - EOS Canada [@abourget]: It's only is eosio.bios
  289. 28.05.2018 08:15:16, Alexandre Bourget - EOS Canada [@abourget]: That's why we're doing that dance in the bootseq (system to bios, setprods, bios to system)
  290. 28.05.2018 08:15:54, Michael Yeates [@michaelyeates]: can we try to keep to validation requirements
  291. 28.05.2018 08:16:04, Michael Yeates [@michaelyeates]: what do we need to validate a particular chain
  292. 28.05.2018 08:16:14, Alexandre Bourget - EOS Canada [@abourget]: Also, schedule from setprods isn't altered until 15% votes threshold
  293. 28.05.2018 08:17:06, Sharif Bouktila - EOS Dublin [@sharifbouktila]: @abourget try think of what you would need to do to validate a chain which you weren’t involved in launching.
  294. 28.05.2018 08:17:37, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We are trying to come up with a launch agnostic approach here
  295. 28.05.2018 08:19:30, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Is this a soft setting from your boot process or a hard setting in the eosio code?
  296. 28.05.2018 08:21:11, WinLin-EOSBIXIN [@hiwinlin]: by the validation, I have found something:
  297. 1. TESTNET_TRUNCATE_SNAPSHOT: 1000 will inject 1001 indeed
  298. 2. do we need to create eosio.unregd account? and why issue 758877.2060 to eosio.unregd?
  299. @abourget
  300. 28.05.2018 08:22:41, WinLin-EOSBIXIN [@hiwinlin]: eos-bios should export a csv file which contains all the account was created in the boot progress
  301. 28.05.2018 08:24:09, WinLin-EOSBIXIN [@hiwinlin]: in the first time when I validate the chain, I got failed just because I don't know the create producer or eosio.uregd accounts
  302. .....28.05.2018 08:26:31, Patryk @perduta from Tokenika [@perduta]: >>unsupported service message type: messageActionChatJoinedByLink<<
  303. .....28.05.2018 08:28:25, Craig Murray - EOS BlockSmith [@craigmurray100]: >>unsupported service message type: messageActionChatJoinedByLink<<
  304. .....28.05.2018 08:32:57, Ricardo Marlière - EOS Brazil [@rbmarliere]: >>unsupported service message type: messageActionChatJoinedByLink<<
  305. .....28.05.2018 08:33:10, heipacker eosunion [@heipacker]: >>unsupported service message type: messageActionChatJoinedByLink<<
  306. 28.05.2018 08:38:34, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Hi All
  307.  
  308. I’ve pinned the Google Document we are using.
  309.  
  310. Please read and add any questions / requirements you feel need to be included in our EOS Validation Test Plan
  311.  
  312. The end goal here is an agreement on how a chain should be validated as mainnet.
  313.  
  314. Once the agreed Validation is complete each team should be comfortable to publicly declare the EOS Mainnet.
  315. .....28.05.2018 08:41:57, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: >>unsupported service message type: messageActionChatJoinedByLink<<
  316. .....28.05.2018 08:42:51, Chitty 🅑 - EOS Argentina [@JChitty]: >>invited mini - EOS Argentina [@moonxor]<<
  317. 28.05.2018 09:03:01, Alexandre Bourget - EOS Canada [@abourget]: yes!! that's what I want as questions.. what can I provide that helps others validate ? I'll put that on the list !
  318. 28.05.2018 09:03:57, Alexandre Bourget - EOS Canada [@abourget]: what not export all the actions ? we could inspect the actions ?
  319. 28.05.2018 09:04:00, Alexandre Bourget - EOS Canada [@abourget]: wouldn't that be easier ?
  320. 28.05.2018 09:04:15, Alexandre Bourget - EOS Canada [@abourget]: if the actions are spit in a .jsonl file.. and we have confirmation that these actions are on chain..
  321. 28.05.2018 09:04:29, Alexandre Bourget - EOS Canada [@abourget]: checking against the action list might be also a good solution
  322. 28.05.2018 09:04:44, Alexandre Bourget - EOS Canada [@abourget]: I propose a video call to go through boot sequence proposals..
  323. .....28.05.2018 09:09:18, Eugene Luzgin - EOS Tribe [@eluzgin]: >>unsupported service message type: messageActionChatJoinedByLink<<
  324. 28.05.2018 09:10:05, Eugene Luzgin - EOS Tribe [@eluzgin]: Hello, just joined, catching up on messages here.
  325. 28.05.2018 09:12:18, mao EOSREAL [@maoyifeng]: sharif, do we fix the call time now?
  326. 28.05.2018 09:12:33, mao EOSREAL [@maoyifeng]: it's 9pm in BJ/HK/SG
  327. .....28.05.2018 09:13:51, Issay@OracleChain [@issayTseng]: >>unsupported service message type: messageActionChatJoinedByLink<<
  328. 28.05.2018 09:14:56, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Let’s leave it for now , it might be better to do calls / deep dives in smaller groups and then combine notes.
  329.  
  330. What does @everyone think ??
  331. 28.05.2018 09:16:11, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Again the goal is to agree a Validation approach and test plan which an independent team could use to validate Mainnet
  332.  
  333. It should work regardless of the boot approach.
  334. 28.05.2018 09:16:46, Michael Yeates [@michaelyeates]: it would be easier but a validation script cannot rely on anything provided by the boot
  335. 28.05.2018 09:39:48, Alexandre Bourget - EOS Canada [@abourget]: @winlineosbixin is demo'ing his validation in the Zoom meeting right now!
  336. 28.05.2018 09:40:11, Alexandre Bourget - EOS Canada [@abourget]: [[Webpage]]https://zoom.us/j/717170235
  337. .....28.05.2018 09:52:31, Leonard Dorlöchter - EOS network by Advanced Blockchain AG [@EOSnetwork]: >>unsupported service message type: messageActionChatAddUsers<<
  338. .....28.05.2018 09:56:39, Leonard Dorlöchter - EOS network by Advanced Blockchain AG [@EOSnetwork]: >>invited Anthony Lhériau | EOS Network by Advanced Blockchain AG [@alheriau]<<
  339. 28.05.2018 10:15:49, Alexandre Bourget - EOS Canada [@abourget]: woops :) next version will have 1000 equal 1000 :)
  340. 28.05.2018 10:16:24, Alexandre Bourget - EOS Canada [@abourget]: I think it makes sense to review the unregd pattern together.
  341.  
  342. What about doing a videoconf with those involved in validation ?
  343. 28.05.2018 10:18:22, WinLin-EOSBIXIN [@hiwinlin]: ok
  344. 28.05.2018 10:19:42, WinLin-EOSBIXIN [@hiwinlin]: @abourget I have send you some suggestion please check to make the validate tool works w ell
  345. 28.05.2018 10:30:38, Alexandre Bourget - EOS Canada [@abourget]: thanks, I'll have eos-bios export all actions into a .jsonl file
  346. 28.05.2018 10:42:01, Alexandre Bourget - EOS Canada [@abourget]: ALL:
  347.  
  348. Can we have a videoconf around 1700 UTC ?
  349. 28.05.2018 10:44:20, WinLin-EOSBIXIN [@hiwinlin]: it's 11:00 AM in beijing, I think it's ok
  350. 28.05.2018 10:45:09, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I can join at 17:00 UTC today to facilitate.
  351.  
  352. @abourget what is the agenda?
  353.  
  354. I suggest we take some time to review the Pinned Document also.
  355. 28.05.2018 10:45:27, Alexandre Bourget - EOS Canada [@abourget]: Agenda would be review of bootseq
  356. 28.05.2018 10:45:41, Alexandre Bourget - EOS Canada [@abourget]: And how to validate it.
  357. 28.05.2018 11:00:23, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Can we agree that we need the same Validation approach to work regardless of the boot process ?
  358. 28.05.2018 11:35:46, Eric - sw/eden [@xebb82]: Is this 25minutes from now?
  359. 28.05.2018 11:36:12, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: non stop video conferences this morning. Lol
  360. 28.05.2018 12:38:49, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Yes that’s the plan , who can Join??
  361. 28.05.2018 12:40:02, Eric - sw/eden [@xebb82]: I can join in. Had to run away to buy a mic, but I'm back now.
  362. 28.05.2018 12:40:42, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: Craig and I are available
  363. 28.05.2018 12:41:37, Eric - sw/eden [@xebb82]: Do we have a link for that call?
  364. 28.05.2018 12:42:15, Alexandre Bourget - EOS Canada [@abourget]: didn't put any link yet.. it's still in 15 minutes ?
  365. 28.05.2018 12:44:44, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Yes, can you provide the Zoom Alex?
  366. 28.05.2018 12:50:43, Sharif Bouktila - EOS Dublin [@sharifbouktila]: For 100% clarity here we are joining this call to discuss how we agree an validation approach which could be used regardless of the Boot/Launch process. - Agreed ?
  367. 28.05.2018 12:50:57, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: agreed
  368. 28.05.2018 12:51:17, Alexandre Bourget - EOS Canada [@abourget]: Yes
  369. 28.05.2018 12:51:41, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: would be counterproductive to fall into a "which boot process is best" conversation
  370. 28.05.2018 12:52:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Ok lets keep it to 30 Mins
  371. 28.05.2018 12:52:26, Alexandre Bourget - EOS Canada [@abourget]: no no.. that's not the point.. I might use a yaml used in the process for the sake of discussion here.. hope it won't offend :) but it's more about the process.. and the actions..
  372. 28.05.2018 12:52:27, Alexandre Bourget - EOS Canada [@abourget]: 8 minutes now
  373. 28.05.2018 12:52:38, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Have you got a link
  374. 28.05.2018 12:52:45, Ricardo Marlière - EOS Brazil [@rbmarliere]: will it be in zoom or something else web based?
  375. 28.05.2018 12:54:43, Eric - sw/eden [@xebb82]: I can launch a zoom if needed.
  376. 28.05.2018 12:54:56, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Go for it
  377. 28.05.2018 12:55:09, Alexandre Bourget - EOS Canada [@abourget]: [[Webpage]]https://zoom.us/j/849742198
  378. 28.05.2018 12:56:40, Alexandre Bourget - EOS Canada [@abourget]: Someone might want to pin it..
  379. .....28.05.2018 13:14:59, Marshall - SaltBlock [@marshallslc]: >>unsupported service message type: messageActionChatJoinedByLink<<
  380. .....28.05.2018 13:38:56, Adrian - SaltBlock [@adrian_saltblock]: >>unsupported service message type: messageActionChatJoinedByLink<<
  381. 28.05.2018 15:25:54, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Great call, thanks to everyone that joined.
  382.  
  383. For those who didn't much was discussed. I believe everyone needs to work together from here on in.
  384.  
  385. I like the proposal of pausing the chain for a period (24 hours) to propose a "Validation Candidate" and let everyone at it.
  386.  
  387. If we can agree this approach I don't think it matters what approach we use to launch it.
  388. 28.05.2018 15:26:36, Michael Yeates [@michaelyeates]: 👍 sorry i could not make it but it sounded like it was productive
  389. 28.05.2018 15:26:51, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We should just aim to publish guidelines to how the community at large can validate for themselves
  390. 28.05.2018 15:26:53, Eric - sw/eden [@xebb82]: If it's not agreed that the chain validated correctly we could switch launch software tool
  391. 28.05.2018 15:27:34, Michael Yeates [@michaelyeates]: how long do we think it would take to validate, we would need a lot of individual confirmations over time
  392. 28.05.2018 15:28:14, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We were suggesting 24 hours, and then open it up for voting / staking and see if it gets to 15%
  393. 28.05.2018 15:28:21, Sharif Bouktila - EOS Dublin [@sharifbouktila]: If no issues
  394. 28.05.2018 15:28:51, Michael Yeates [@michaelyeates]: what about software testing?
  395. 28.05.2018 15:28:52, Charles H - EOS 42 [@ankh2054]: [[Webpage]]http://producer.vote
  396. 28.05.2018 15:28:57, Roman CryptoLions [@romanskaskiw]: +
  397. 28.05.2018 15:29:19, Charles H - EOS 42 [@ankh2054]: Sharing the above - proxy voting pool. Hopefully this will help get to 15% faster.
  398. 28.05.2018 15:29:32, Sharif Bouktila - EOS Dublin [@sharifbouktila]: One suggestion I have on the weighting of BPs in BIOS that rather than 1-100 , it should be that a BP flags the ones that they know vs the ones that they don't. 1 or 0
  399. 28.05.2018 15:30:16, Charles H - EOS 42 [@ankh2054]: +1 on that idea. You know them plus you vouch for their technical ability.
  400. 28.05.2018 15:30:33, Charles H - EOS 42 [@ankh2054]: Or trust their technical ability.
  401. 28.05.2018 15:31:09, Michael Yeates [@michaelyeates]: 24 hours seems very rushed to me
  402. 28.05.2018 15:31:55, Eric - sw/eden [@xebb82]: +1, but I think we'll have time before its active 🤷‍♂
  403. 28.05.2018 15:31:57, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We could say 24-72 hours, and make a call. If all validation checks are passing we can push on
  404. 28.05.2018 15:32:33, Eric - sw/eden [@xebb82]: We basically need to test all functionality that we can think of.
  405. 28.05.2018 15:32:57, Michael Yeates [@michaelyeates]: 15% is basically 2 people voting. i think validation will be very quick
  406. 28.05.2018 15:33:11, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Lets try get those test conditions in a document before
  407. 28.05.2018 15:33:47, Eric - sw/eden [@xebb82]: Sure. I'll help contribute to it.
  408. I have one started on one of my computers...
  409. 28.05.2018 15:34:05, Sharif Bouktila - EOS Dublin [@sharifbouktila]: throw it into the google doc pinned as a start
  410. 28.05.2018 15:35:54, Sharif Bouktila - EOS Dublin [@sharifbouktila]: The other questions we had was:
  411.  
  412. 1. How to validate the snapshot?
  413. 2. Who can and is taking snapshots over the coming days as dry runs
  414. 3. Once we have a snapshot, what time do we start working at on June 2nd ??
  415.  
  416. My vote is sometime around 2pm UTC
  417. .....28.05.2018 15:55:48, Craig Murray - EOS BlockSmith [@craigmurray100]: >>invited Syed Jafri | EOS Cafe / Calgary [@syed_jafri]<<
  418. 28.05.2018 15:56:46, Michael Yeates [@michaelyeates]: just a hash of the file should be ok for the snapshot
  419. 28.05.2018 15:59:58, Ricardo Marlière - EOS Brazil [@rbmarliere]: this
  420. 28.05.2018 16:00:03, Eric - sw/eden [@xebb82]: 1. Compare with each other. Maybe publish online to allow people to look for their keys and balances...?
  421.  
  422. 2. I will look into running the snapshot creation process on multiple machines. Should be able to do it on at least 5...
  423. 28.05.2018 16:00:11, Craig Murray - EOS BlockSmith [@craigmurray100]: just want to say that that last meeting was pretty outstanding in my view. A great deal of ground was covered and I think we're getting MUCH closer to the point where the very top technical groups are going to be ABPs on the same chain.
  424. 28.05.2018 16:00:23, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Syncing parity takes days, better get started soon
  425. 28.05.2018 16:00:28, Eric - sw/eden [@xebb82]: +1
  426. 28.05.2018 16:00:40, Michael Yeates [@michaelyeates]: think eosauthority are doing this
  427. 28.05.2018 16:00:58, Eric - sw/eden [@xebb82]: Have it synced already. Thinking of starting from that synced chain but on multiple machines.
  428. The chain should be the same... Right? :)
  429. 28.05.2018 16:02:12, Ricardo Marlière - EOS Brazil [@rbmarliere]: 1 yes definitely
  430. 28.05.2018 16:02:34, Sam - EOS Dublin [@samnoble]: Is there a guid to getting this up and running? We can spin up a box to run this on
  431. 28.05.2018 16:03:06, Igor Lins e Silva - EOS Rio [@igorls]: @EOSIOSnapshot
  432. 28.05.2018 16:03:27, Sam - EOS Dublin [@samnoble]: Thanks
  433. 28.05.2018 16:54:24, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]Just posted this - URGENT & AWESOME - https://medium.com/@eosdublin/urgent-awesome-f3e310a4cd42
  434. .....28.05.2018 17:40:54, Roshan - EOS Authority [@telepound]: >>unsupported service message type: messageActionChatJoinedByLink<<
  435. 28.05.2018 17:42:51, Roshan - EOS Authority [@telepound]: Yes. We have been running the snapshot code for quite some time now. The new fallback method works well too.
  436. 28.05.2018 17:46:38, Michael Yeates [@michaelyeates]: has anyone thought about the requirements for external tools such as wallets before we launch?
  437. 28.05.2018 17:46:45, Michael Yeates [@michaelyeates]: is block one making one?
  438. 28.05.2018 17:46:59, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Yes scatter is making one, I do not think block.one will release one right now
  439. 28.05.2018 17:47:22, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I have been working on a paper wallet
  440. 28.05.2018 17:47:37, Michael Yeates [@michaelyeates]: we need to have something ready or there will be so many scam wallets filling the void
  441. 28.05.2018 17:47:45, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Any idea when after the freeze when a snapshot will be available ?
  442.  
  443. Trying to piece together a rough timeline for launch.
  444. 28.05.2018 17:48:11, Ricardo Marlière - EOS Brazil [@rbmarliere]: i believe scatter will be ready by then
  445. 28.05.2018 17:48:36, Michael Yeates [@michaelyeates]: is it something else? nathan keeps saying scatter isnt a wallet
  446. 28.05.2018 17:49:08, Ricardo Marlière - EOS Brazil [@rbmarliere]: I thought we could sign transactions with it?
  447. 28.05.2018 17:49:11, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I think they built a wallet
  448. 28.05.2018 17:49:31, Roshan - EOS Authority [@telepound]: The snapshot run can take anywhere from 3 hours to 6 hours. Assuming you have a fully synced parity node. I assume we will have it within 6 hours of freeze max.
  449. .....28.05.2018 17:50:35, Roshan - EOS Authority [@telepound]: >>invited Rohan - EOSauthority [@RohanWillAnswer]<<
  450. 28.05.2018 17:51:17, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I can probably find it but what time is freeze on the 1st ?
  451. 28.05.2018 17:51:55, Michael Yeates [@michaelyeates]: lets be careful with expectations on a time frame here
  452. 28.05.2018 17:52:03, Michael Yeates [@michaelyeates]: better to over deliver
  453. 28.05.2018 17:52:15, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I’m just try suggest the start
  454. 28.05.2018 17:52:41, Roshan - EOS Authority [@telepound]: ERC20 EOS tokens are frozen 23 hours after June 1, 2018 at 22:59:59 UTC. So June 2nd 21:59:59
  455. 28.05.2018 17:52:46, Roshan - EOS Authority [@telepound]: 👍
  456. 28.05.2018 17:54:06, Sharif Bouktila - EOS Dublin [@sharifbouktila]: So snapshots ready circa 04:00 UTC 3rd June ?
  457. 28.05.2018 17:55:54, Roshan - EOS Authority [@telepound]: Let's say latest 8 am UTC
  458. 28.05.2018 17:56:18, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Ok cool
  459. 28.05.2018 17:58:47, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Have we agreed on an onchain validation from these snapshots
  460. 28.05.2018 17:59:01, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Last time I checked, I believe the different tools were not matching up
  461. 28.05.2018 17:59:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: On which chain?
  462. 28.05.2018 17:59:46, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Like the chain that is going to be launched
  463. 28.05.2018 17:59:52, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I never tested myself but I heard concerns
  464. 28.05.2018 17:59:56, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: of no consensus between tools
  465. 28.05.2018 18:00:30, Sharif Bouktila - EOS Dublin [@sharifbouktila]: nothing is agreed yet
  466. 28.05.2018 18:02:09, Rohan - EOSauthority [@RohanWillAnswer]: I’ve synced up to period 345. If anyone has a snapshot.json to compare with mine? I will send mine tomorrow.
  467. 28.05.2018 18:12:55, Michael Yeates [@michaelyeates]: i think we should avoid consensus with which tool to use, they should all agree that the tokens on-chain match those in the snapshot
  468. .....28.05.2018 18:15:23, Robert DeWilder - Worbli [@BrownDonahue]: >>unsupported service message type: messageActionChatJoinedByLink<<
  469. 28.05.2018 18:22:13, Rohan - EOSauthority [@RohanWillAnswer]: Bodhan and I compared our versions few days ago. Period 342 and ran a simple diff to get quite a few discrepancies including in the snapshot.json files
  470. 28.05.2018 18:24:42, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Hmm, any idea why?
  471. 28.05.2018 18:30:40, Rohan - EOSauthority [@RohanWillAnswer]: There were quite a lot of differences. When I run it a couple of times after a truncate for example, the output matches exactly what I got both times.
  472. 28.05.2018 18:33:05, Rohan - EOSauthority [@RohanWillAnswer]: We seem to be missing @sandw1ch here. Any reason we can’t have him here? His expertise will be invaluable.
  473. 28.05.2018 18:35:21, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I’ve no issue
  474. 28.05.2018 18:35:58, Sharif Bouktila - EOS Dublin [@sharifbouktila]: The more positive contribution the better!
  475. 28.05.2018 18:38:11, David P - EOS42 [@GunnisonCap]: Block.one cannot have anything to do with the launch
  476. 28.05.2018 18:39:05, David P - EOS42 [@GunnisonCap]: I would suggest they will ask to not be included. Referencing them directly for views is probably the best course.
  477. 28.05.2018 18:40:53, Rohan - EOSauthority [@RohanWillAnswer]: I suspected that might be the case and wanted to check.
  478. 28.05.2018 18:42:59, David P - EOS42 [@GunnisonCap]: Yep well worth it, there’s a few we would all benefit from being here right now - we’re on our own to work through all this now. We need daily calls like the one today going forward.
  479. 28.05.2018 18:48:05, Michael Yeates [@michaelyeates]: discussion about validating snapshot.csv files should be in the snapshot channel. we can check that given a consistent input, we can provide consistent validation of the on chain balances. this should happen regardless of the boot method
  480. 28.05.2018 18:49:09, Kevin Rose - EOS New York [@eosnewyork]: Hey all. Cypherglass asked me to add them. In the spirit of including those who wish to contribute, I'm going to oblige.
  481. 28.05.2018 19:10:30, aza eosar [@p17er0bl3do]: been thinking, both methods of validation (freeze/snap) that have been proposed have the same basic requirements, agree on a block, check the state there, avoid before that block any transaction that is not part of the boot sequence. This last part is what i'm more unsure about how to enforce. But if we share beforehand they pubs of all BPCs we can use the peer-key param to exclude everyone who is not a BPC
  482. .....28.05.2018 19:22:05, Kevin Rose - EOS New York [@eosnewyork]: >>invited James Sutherland - Cypherglass.com [@JamesSutherland]<<
  483. .....28.05.2018 19:22:26, Kevin Rose - EOS New York [@eosnewyork]: >>invited Adrianna Mendez - Cypherglass [@AdriMendez]<<
  484. .....28.05.2018 20:33:51, James Sutherland - Cypherglass.com [@JamesSutherland]: >>invited Ross - Cypherglass [@Ross_Cypherglass]<<
  485. .....28.05.2018 20:34:26, Adrianna Mendez - Cypherglass [@AdriMendez]: >>unsupported service message type: messageActionChatAddUsers<<
  486. 28.05.2018 20:40:11, Eric - sw/eden [@xebb82]: Yes, this was discussed as one of the possible solutions to that problem. Works very well in combination with the pause command.
  487. 28.05.2018 20:45:54, Michael Yeates [@michaelyeates]: all of the ricardian contracts is something we need to think about for chain validation. they need to be in the codebase and agreed before launch
  488. 28.05.2018 20:46:29, Kevin Rose - EOS New York [@eosnewyork]: My understanding is that there is no constitution ratification period now. What we load up will be the constitution.
  489. 28.05.2018 20:46:50, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Really..
  490. 28.05.2018 20:47:45, Kevin Rose - EOS New York [@eosnewyork]: Tokens are unlocked after staking period. Constitutional Hash (CH) will start signing all transactions immediately. Basically ratified at chain activation which means what we load is the constitution.
  491. 28.05.2018 20:48:06, Kevin Rose - EOS New York [@eosnewyork]: Correct me if I'm wrong, please.
  492. 28.05.2018 20:49:53, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I think you are right..which means voters have to agree to it or get off the only EOS chain
  493. 28.05.2018 20:50:00, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Just seems wrong
  494. 28.05.2018 20:51:44, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Nothing is locked... only block pay, based on reading the eosio contracts
  495. 28.05.2018 20:52:43, Eric - sw/eden [@xebb82]: The schedule.
  496. 28.05.2018 20:52:57, Kevin Rose - EOS New York [@eosnewyork]: I know the recent launch conference call discussed not staking all tokens by default but what you're saying is contrary to what I understood. I thought all tokens are staked for bandwidth by default at the moment of issuance. They are only available for reclamation after the 3 day staking period has ended. Am I wrong?
  497. 28.05.2018 20:54:22, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Wow, I missed that call (thanks Aussie time). If that's true, that would seem to be up to the boot process. I'd be pretty pissed if my personal tokens were already staked
  498. 28.05.2018 20:54:50, Nathan Rempel | GenerEOS Sydney [@nsrempel]: What if i wanted to use those to create a new account and deploy a smart contract right away? I'd be furious
  499. 28.05.2018 20:56:05, Eric - sw/eden [@xebb82]: I'd be furious if someone decided that I can't create whichever account name I wanted, but that they themselves reserved "b1".
  500. 28.05.2018 20:56:15, Michael Yeates [@michaelyeates]: lol
  501. 28.05.2018 20:57:00, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Create your own blockchain and you can have all the names you want :)
  502. 28.05.2018 20:57:38, Eric - sw/eden [@xebb82]: 😂
  503. 28.05.2018 20:58:10, Kevin Rose - EOS New York [@eosnewyork]: We said one mainnet Nathan! One! 😂
  504. 28.05.2018 20:58:19, Ross (EOSphere) [@rossco99]: hah!
  505. 28.05.2018 20:58:31, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I have heard the schedule is locked, though I didn't hear whether that was by the boot bios or if its built in? Can someone link the github code?
  506. 28.05.2018 20:59:39, Nathan Rempel | GenerEOS Sydney [@nsrempel]: One EOS mainnet, but sw/eden can create their own blockchain core code if they wanted ;)
  507. 28.05.2018 20:59:40, Michael Yeates [@michaelyeates]: its built in
  508. 28.05.2018 21:00:17, Michael Yeates [@michaelyeates]: or in the system contract, sorry.. late
  509. 28.05.2018 21:00:42, Nathan Rempel | GenerEOS Sydney [@nsrempel]: @michaelyeates that makes sense. i suppose theirs no provision that "forces" the original producers out? they can still be voted for at the moment?
  510. 28.05.2018 21:02:08, Michael Yeates [@michaelyeates]: no, and i think they have to keep producing irreversible blocks
  511. 28.05.2018 21:02:25, Michael Yeates [@michaelyeates]: otherwise voting will not work and we have a dead chain
  512. 28.05.2018 21:02:54, Michael Yeates [@michaelyeates]: thats why i would prefer to keep many chains open during the validation phase
  513. 28.05.2018 21:06:01, Nathan Rempel | GenerEOS Sydney [@nsrempel]: yeah i agree the original ABP will keep producing blocks... just wasn't sure if their is a distinction between "boot producers" and "voted producers" in the codebase
  514. 28.05.2018 21:06:18, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I would also prefer to keep the chains open and active if possible
  515. .....28.05.2018 22:32:53, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>invited Patrick B - Aloha EOS<<
  516. .....28.05.2018 22:41:38, Patrick B - Aloha EOS: >>invited Nate D - Aloha EOS [@n8dee]<<
  517. .....28.05.2018 22:43:42, Jae Chung - HKEOS [@jaechung]: >>invited Santhosh EOSNodeOne [@kamsa74]<<
  518. .....28.05.2018 23:37:00, Santhosh EOSNodeOne [@kamsa74]: >>invited Robinson EOS NodeOne [@aweekago]<<
  519. .....29.05.2018 00:21:28, Joe EOS Asia [@gaijinJOE]: >>unsupported service message type: messageActionChatJoinedByLink<<
  520. .....29.05.2018 00:59:24, Heejae - EOSYS.io [@heejaejoo]: >>unsupported service message type: messageActionChatJoinedByLink<<
  521. .....29.05.2018 02:39:25, nahu [@naueh]: >>unsupported service message type: messageActionChatJoinedByLink<<
  522. 29.05.2018 03:26:52, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Morning / Afternoon / Evening @everyone
  523.  
  524. To the new guys in here, we have a Google Doc pinned , please review and add / comment as you see fit.
  525.  
  526. We will be organising another call today.
  527.  
  528. How many can make a call at 17:00 UTC ??
  529. 29.05.2018 04:27:13, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Some questions
  530.  
  531. We said yesterday that anyone should be able to validate the snapshot and we should allow anyone to run their own tests to validate the chain.
  532.  
  533. 1. How should someone outside the launch group make contact to flag an issue?
  534.  
  535. 2. What channel should we use to communicate progress / Milestones to the outside world? eg. Chain is validated / Open for Staking / Mainnet ??
  536.  
  537. 3. Where do we publish endpoints?
  538. 29.05.2018 04:36:49, Eric - sw/eden [@xebb82]: Please explain why you think pausing is a bad idea.
  539. 29.05.2018 04:44:00, Adrian - SaltBlock [@adrian_saltblock]: So many new names and faces. :)
  540. .....29.05.2018 05:15:30, Pete BlockMatrix [@blockmatrixpete]: >>unsupported service message type: messageActionChatJoinedByLink<<
  541. 29.05.2018 05:18:56, aza eosar [@p17er0bl3do]: i don't see any improvement on taking a snapshot and we can use that time it runs to test its stable and clear any doubts on its stability to other potencial boot groups. The idea is to call pause on all producers?
  542. What's really a bad idea (to me) is modifying the contracts to fit our needs as BPC at boot, we should keep EOS as vanilla as possible, but dont know if thats still on the table.
  543. 29.05.2018 05:27:26, Eric - sw/eden [@xebb82]: 1. How do we take a snapshot?
  544. 2. Do we really want to test stability on the live production chain before it has been accepted as validated?
  545. We have to run multiple chains to test all functionality anyways? Isn't it at this point better to focus on that?
  546. 3. I agre on the contracts. It's not needed.
  547. 29.05.2018 05:28:19, Eric - sw/eden [@xebb82]: Yea, the idea is to call pause on all producers to allow 24? 48? 72? hours to validate the chain.
  548. Allow anyone to connect in and validate the state of the blockchain before we start accepting votes and other transactions.
  549. 29.05.2018 05:29:20, David P - EOS42 [@GunnisonCap]: How long is required for validation? I don’t understand in my simple perspective why we would talk about up to 3 days for validation?
  550. 29.05.2018 05:30:46, Eric - sw/eden [@xebb82]: We want everyone in the community to get the chance to validate everything.
  551. We aren't even sure that the snapshot generation tool will work. We want to know if we missed some account or balance from the ERC20 distribution. It's not just us active producer candidates that should do validation.
  552. 29.05.2018 05:32:09, Eric - sw/eden [@xebb82]: Possibly we need more than 72 hours, since ... if people haven't pre-synced parity, it takes 3 days just to sync that to actually be able to create their own snapshots to validate against.
  553. 29.05.2018 05:32:59, Eric - sw/eden [@xebb82]: We are launching a multi billion dollar network. This can't be stressed enough.
  554. Normally the test phase should be weeks or months for basically any fix that's added.
  555. 29.05.2018 05:33:43, Adrian - SaltBlock [@adrian_saltblock]: This.
  556. 29.05.2018 05:34:30, Sharif Bouktila - EOS Dublin [@sharifbouktila]: But it needs to be agreed and clearly communicated
  557. 29.05.2018 05:34:38, Adrian - SaltBlock [@adrian_saltblock]: Given the sheer amount of eyes on this blockchain project, we really can't afford to get it wrong based on something we could have sorted out through proper validation (which at this point, does indeed seem a bit impossible)
  558. 29.05.2018 05:34:46, Sharif Bouktila - EOS Dublin [@sharifbouktila]: And we need to have a forum / method for that communication
  559. 29.05.2018 05:35:03, Eric - sw/eden [@xebb82]: 👍
  560. 29.05.2018 05:35:54, Issay@OracleChain [@issayTseng]: http://blogs.360.cn/blog/eos-node-remote-code-execution-vulnerability/
  561. 29.05.2018 05:36:18, Issay@OracleChain [@issayTseng]: 360 Says EOS Epic Vulnerability Can Be Fully Controlled by Trading Detonation System
  562. .....29.05.2018 05:37:54, Matthew Bryce 马修·布赖斯 - BitSpace [@matthewbryce]: >>invited James David Tandy - 詹姆士 - Bitspace [@jimmythesaint]<<
  563. 29.05.2018 05:43:28, David P - EOS42 [@GunnisonCap]: So in essence we need to communicate out clearly to the global community that there will be a complete freeze on all EOS token trading for nearly a week in that case. That's not going to down well with them.
  564. 29.05.2018 05:43:40, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Can I propose we have 4 phases to communicate
  565.  
  566. Launch - Snapshot Verification & BIOS Boot
  567. Pause - Validation
  568. Enable - Open for staking until 15%
  569. Release - Declaration of Mainnet
  570. 29.05.2018 05:44:20, David P - EOS42 [@GunnisonCap]: I don't really get it - if a number of trusted parties validate, then what's to stop the chain launching? If others want to retrospectively validate as well then they can.
  571. 29.05.2018 05:44:31, David P - EOS42 [@GunnisonCap]: I don't understand why we're talking about such a long time period.
  572. 29.05.2018 05:44:49, Eric - sw/eden [@xebb82]: Until recent changes to the code this is how we had been told it should work.
  573. 29.05.2018 05:45:24, Eric - sw/eden [@xebb82]: 👏
  574. 29.05.2018 05:45:32, David P - EOS42 [@GunnisonCap]: That makes complete sense - we need a joint statement from as many BP's as possible on this approach if agreed.
  575. 29.05.2018 05:45:34, Michael Yeates [@michaelyeates]: before launch we will need snapshot validation
  576. 29.05.2018 05:45:41, Michael Yeates [@michaelyeates]: otherwise great :)
  577. 29.05.2018 05:46:10, Eric - sw/eden [@xebb82]: +1
  578. 29.05.2018 05:46:18, Charles H - EOS 42 [@ankh2054]: have we figures out a way to pause reliably?
  579. 29.05.2018 05:46:22, Eric - sw/eden [@xebb82]: yes
  580. 29.05.2018 05:46:22, Igor Lins e Silva - EOS Rio [@igorls]: 👍
  581. 29.05.2018 05:46:26, Charles H - EOS 42 [@ankh2054]: great :)
  582. 29.05.2018 05:46:27, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Launch - Snapshot Verification & BIOS Boot
  583. Pause - Validation
  584. Enable - Open for staking until 15%
  585. Release - Declaration of Mainnet
  586. 29.05.2018 05:46:34, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Lets keep it as 4 phases
  587. 29.05.2018 05:46:44, Adrian - SaltBlock [@adrian_saltblock]: I think that sounds good Sharif.
  588. 29.05.2018 05:47:40, Eric - sw/eden [@xebb82]: I'm all for that. Great idea Sharif.
  589. 29.05.2018 05:47:49, Michael Yeates [@michaelyeates]: does anyone have any thoughts on generation and validation of the snapshot?
  590. 29.05.2018 05:48:01, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Rollback and restart is possible at any phase before RELEASE - that should be the message.
  591. 29.05.2018 05:48:39, Eric - sw/eden [@xebb82]: +1 on that
  592. 29.05.2018 05:50:44, Charles H - EOS 42 [@ankh2054]: +1
  593. 29.05.2018 05:50:54, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We don't then have to give time lines. If we agree what Validation is needed, once its complete we can move to Enable
  594. 29.05.2018 05:51:05, Eric - sw/eden [@xebb82]: Open for "voting", all will be staked already. right?=
  595. 29.05.2018 05:51:41, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I believe so
  596. 29.05.2018 06:51:02, aza eosar [@p17er0bl3do]: i guess we can both take the snap and pause it, just lets make a test of pausing it to see we can recover ok from it
  597. 29.05.2018 06:54:24, Eric - sw/eden [@xebb82]: We have tested pausing chains many times already. But yes. There are a lot we need to test, and the pause time is perfect for that.
  598. The ABPs just fork up another chain. And test on that one.
  599. 29.05.2018 06:56:12, David P - EOS42 [@GunnisonCap]: So I'm clear, when and how do we agree that "validation is complete" as opposed to "completed by some"?
  600. 29.05.2018 06:56:37, Kevin Rose - EOS New York [@eosnewyork]: We need to very clearly set expectations to the world. Sharif you should draft another joint statement that each BP can publish.
  601. 29.05.2018 06:56:48, Michael Yeates [@michaelyeates]: i guess we would create a window and then if no bad reports come in we move on
  602. 29.05.2018 06:57:02, Kevin Rose - EOS New York [@eosnewyork]: It needs to be communicated as soon as possible
  603. 29.05.2018 06:57:10, David P - EOS42 [@GunnisonCap]: And my view is that we have a responsibility to clearly set expectations for the community - we can't sit here saying "we don't have to give timelines". I think we do need to communicate something clearly and soon.
  604. 29.05.2018 06:57:16, David P - EOS42 [@GunnisonCap]: Ah, yes - same as Kevin says.
  605. 29.05.2018 06:57:32, Michael Yeates [@michaelyeates]: igor is preparing a flowchart on mainnet launch
  606. 29.05.2018 06:57:39, Michael Yeates [@michaelyeates]: he will share in a moment
  607. 29.05.2018 06:58:17, David P - EOS42 [@GunnisonCap]: That seems the only logical way - nothing reported after say 12hrs (or whatever is agreed), considered validated and move on
  608. 29.05.2018 06:58:27, David P - EOS42 [@GunnisonCap]: Great
  609. 29.05.2018 07:06:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We’ll aim to get a statement ready for tomorrow
  610.  
  611. @GunnisonCap @eosnewyork can you round the groups so they are prepared like the one which went out on Friday ?
  612. 29.05.2018 07:09:59, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We also need to decide how we communicate Endpoint(s) available for validation - don’t we??
  613. 29.05.2018 07:11:20, Kevin Rose - EOS New York [@eosnewyork]: Just so we’re saying the same thing the purpose of this statement is to set expectations of launch timing with explanation. We should keep it hyper focused.
  614. 29.05.2018 07:11:46, Kevin Rose - EOS New York [@eosnewyork]: Unless you weren’t suggesting that be added :)
  615. 29.05.2018 07:13:17, David P - EOS42 [@GunnisonCap]: Grand, that should be an aim of today then. I'll talk to @eosnewyork about coordinating this.
  616. 29.05.2018 07:14:59, David P - EOS42 [@GunnisonCap]: Here's a key point, we can give estimated time ranges for the different phases by all means. We don't need to tie ourselves to best case or worst, but setting community expectations is our collective responsibility on this too.
  617. 29.05.2018 07:16:14, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I think just the 4 phases , How we will announce each one and a commitment that we will publish our validation approach.
  618. 29.05.2018 07:17:19, Khosi Morafo eosAfrica [@khosimorafo]: 👏👏👏👏👏👏
  619. 29.05.2018 07:19:32, Roman CryptoLions [@romanskaskiw]: +1
  620. 29.05.2018 07:22:02, Khosi Morafo eosAfrica [@khosimorafo]: 👍👍👍
  621. 29.05.2018 07:23:47, Charles H - EOS 42 [@ankh2054]: If we are to pause the chain and we also need to decide who are the ABP’s to to boot and whether we use wiregaurd VPN OR simply setup firewall rules and OR # peer-key.
  622. 29.05.2018 07:27:02, Kevin Rose - EOS New York [@eosnewyork]: +1
  623. 29.05.2018 07:28:02, Adrian - SaltBlock [@adrian_saltblock]: I was kind of hoping it would show all the +1 in that quote 😉
  624. 29.05.2018 07:28:59, Kevin Rose - EOS New York [@eosnewyork]: Yea me too. Boo telegram
  625. 29.05.2018 07:29:10, Adrian - SaltBlock [@adrian_saltblock]: Feature request.
  626. 29.05.2018 07:29:32, Adrian - SaltBlock [@adrian_saltblock]: (useless, but could get exciting if enough people leveraged the feature...)
  627. 29.05.2018 07:29:35, Kevin Rose - EOS New York [@eosnewyork]: +1
  628. 29.05.2018 07:29:40, Charles H - EOS 42 [@ankh2054]: Should we all nominate some people on our teams to provide community updates
  629. 29.05.2018 07:30:18, Charles H - EOS 42 [@ankh2054]: When we reach each phase we do a collective tweet and publish on a website.
  630. 29.05.2018 07:31:56, Kevin Rose - EOS New York [@eosnewyork]: Have the person with the idea write the original draft every time. Have @GunnisonCap and I execute on it.
  631. 29.05.2018 07:33:23, Khosi Morafo eosAfrica [@khosimorafo]: Well, who are the best communicators? Keeping in mind that should something go wrong, these will be the go-to people for the press.
  632. 29.05.2018 07:33:51, Charles H - EOS 42 [@ankh2054]: +1 for Kevin and David P.
  633. 29.05.2018 07:34:16, Kevin Rose - EOS New York [@eosnewyork]: What I mean is that @GunnisonCap and I work to disseminate the statement to all BPs who agree for publishing. Every BP is an access point for the press. We can’t designate someone for that
  634. 29.05.2018 07:34:48, Charles H - EOS 42 [@ankh2054]: Enable - Open for staking until 15% - on this release would be good to add some links where people can vote.
  635. 29.05.2018 07:36:47, Khosi Morafo eosAfrica [@khosimorafo]: I do not think its a bad thing for the community to have one or two people who will tell a single story. More people may risk more FUD. But I say that accepting that in a distributed system like EOS, some may sulk at the idea.
  636. 29.05.2018 07:38:06, Kevin Rose - EOS New York [@eosnewyork]: Normally I prefer majority buy in on ideas and nominations but we don’t have the luxury of time. Let @GunnisonCap and I worry about taking a drafted statement from the idea creator and getting it out there to every BP. Every BP can publish the statements we edit. We only ever publish statements that the group approves of.
  637. 29.05.2018 07:38:42, Kevin Rose - EOS New York [@eosnewyork]: No one BPs name will ever be on them. They are signed by “EOS Mainnet Launch Group” or something to that effect.
  638. 29.05.2018 07:38:47, Charles H - EOS 42 [@ankh2054]: +1
  639. 29.05.2018 07:38:54, Kevin Rose - EOS New York [@eosnewyork]: And let’s return to the important task of detailing how launch will go.
  640. 29.05.2018 07:41:18, Khosi Morafo eosAfrica [@khosimorafo]: I would have thought properly communicating that very launch is as important. But cool, let's move on.
  641. 29.05.2018 07:42:15, Igor Lins e Silva - EOS Rio [@igorls]: [[Webpage]]https://zoom.us/j/427431126
  642. 29.05.2018 07:42:19, Kevin Rose - EOS New York [@eosnewyork]: No it is, absolutely. Sorry I didn’t mean to sound that way.
  643. 29.05.2018 07:42:25, Igor Lins e Silva - EOS Rio [@igorls]: Join now
  644. .....29.05.2018 07:43:38, Craig Murray - EOS BlockSmith [@craigmurray100]: >>invited Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]<<
  645. 29.05.2018 07:44:12, Khosi Morafo eosAfrica [@khosimorafo]: ☺😉😍
  646. .....29.05.2018 07:44:16, Santhosh EOSNodeOne [@kamsa74]: >>invited Hahn - EOS NodeOne [@hahnryu]<<
  647. 29.05.2018 07:50:12, Kevin Rose - EOS New York [@eosnewyork]: @deckw
  648. 29.05.2018 07:50:22, Eric - sw/eden [@xebb82]: He's in
  649. 29.05.2018 07:51:00, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: Thx!
  650. 29.05.2018 07:54:00, Kevin Rose - EOS New York [@eosnewyork]: Thank you
  651. 29.05.2018 08:30:58, David P - EOS42 [@GunnisonCap]: Interesting call, I'll brief you later
  652. 29.05.2018 08:45:58, Craig Murray - EOS BlockSmith [@craigmurray100]: another amazing meeting. Nothing like deadline pressure to bring everyone together like one big happy family :) props to everyone for their coordination and cooperation
  653. 29.05.2018 09:25:05, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Re: Communications out. I've just nabbed @eoslaunch on Twitter.
  654.  
  655. Could we use that for official communications for Launch and then all the other BPs RT from it?
  656.  
  657. Could the Asian BPs pick it up and recast on WeChat or similar ?
  658.  
  659. If its useless I'm sure some team would fancy launching another BP under that brand 🙂
  660. 29.05.2018 09:26:14, Kevin Rose - EOS New York [@eosnewyork]: I kind of like the idea. Let’s think about this.
  661. 29.05.2018 09:28:09, David P - EOS42 [@GunnisonCap]: I'm certainly hoping for at least another 50 BP's launching between now and June 3, we don't have enough
  662. 29.05.2018 09:35:52, Kevin Rose - EOS New York [@eosnewyork]: Sharif the difficulty I’m seeing is that twitter isn’t the most popular platform for EOS by a long shot and other platforms like WeChat only support org specific channels. It might just be another layer of management rather than helping.
  663. 29.05.2018 09:37:43, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Probably right.
  664. 29.05.2018 09:38:34, David P - EOS42 [@GunnisonCap]: I think the only way is the coordinated BP 'thunderclap' style announcement across multiple of their social media channels globally
  665. 29.05.2018 09:39:06, Michael Yeates [@michaelyeates]: network of communities
  666. 29.05.2018 09:42:26, Kevin Rose - EOS New York [@eosnewyork]: And I know everyone is feverishly working but I want to bring up a very important component to the launch. Even if we have multiple chains that are verified correct by many BPs many of us have agreed to one mainnet. This means we need a method of choosing from the mainnet chain candidates that we have vetted using the tools and processes we have established here. I propose we decide on as simple of a process as possible which randomly chooses a verified correct chain. From there we present it to the community for 3rd party verification and ultimately voting validation and activation.
  667. 29.05.2018 09:45:32, Rohan - EOSauthority [@RohanWillAnswer]: Update on the snapshot mismatch..
  668.  
  669. There was indeed a bug, identified and flagged with mighty sandw1ch.
  670. He has narrowed it to a race condition and will be sending out a patch soon. I will then be able to merge it onto the EOS distribution collective Github as well.
  671.  
  672. This was definitely a problem affected about 190 odd wallets at period 342 and caused the discrepancy on the snapshot.
  673. 29.05.2018 09:47:16, David P - EOS42 [@GunnisonCap]: That's interesting, be good to understand details later when you can expand
  674. 29.05.2018 09:49:32, Sharif Bouktila - EOS Dublin [@sharifbouktila]: From yesterday’s call we had agreed that the core teams will only launch one at a time
  675. 29.05.2018 09:50:33, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Obv others can do other things , but I think we need to position GhostBios as launching Mainnet
  676. 29.05.2018 09:51:07, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I missed call today so I could be weeks behind current thinking
  677. 29.05.2018 09:54:40, Kevin Rose - EOS New York [@eosnewyork]: Yet the BIOS channel is still chugging along. Did they agree to join Ghostbusters? Or did Ghostbusters agree to join BIOS?
  678. 29.05.2018 09:55:01, Sharif Bouktila - EOS Dublin [@sharifbouktila]: It’s a merger
  679. 29.05.2018 09:55:21, Sharif Bouktila - EOS Dublin [@sharifbouktila]: BIOS is needed for launch
  680. 29.05.2018 09:55:44, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Validation will be independent
  681. 29.05.2018 09:56:34, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]https://medium.com/@eosdublin/ghostbios-de69a674d82e
  682. 29.05.2018 09:56:46, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Posted this this morning
  683. 29.05.2018 09:57:15, Kevin Rose - EOS New York [@eosnewyork]: I'm not sure what that tells me.
  684. 29.05.2018 09:57:32, Kevin Rose - EOS New York [@eosnewyork]: Did both groups agree to combine efforts?
  685. 29.05.2018 09:57:38, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Yes
  686. 29.05.2018 09:57:53, Kevin Rose - EOS New York [@eosnewyork]: Oh, well that's wonderful!
  687. 29.05.2018 09:58:18, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Unless something has changed since ...
  688. 29.05.2018 09:58:27, Kevin Rose - EOS New York [@eosnewyork]: Please excuse me as I clearly missed that.
  689. 29.05.2018 10:01:49, Sharif Bouktila - EOS Dublin [@sharifbouktila]: If that’s still the position, it should also be in the BP statements
  690. 29.05.2018 10:02:18, Sharif Bouktila - EOS Dublin [@sharifbouktila]: 1 approach to launch 1 mainnet
  691. 29.05.2018 10:02:40, Kevin Rose - EOS New York [@eosnewyork]: Absolutely
  692. 29.05.2018 10:04:45, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Anyone in here have a different understanding of where we are currently??
  693. 29.05.2018 10:06:23, Charles H - EOS 42 [@ankh2054]: I am on a eos-bios boot right now, but nobody here is running any VPN.
  694. .....29.05.2018 10:37:51, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: >>invited Peter Sveda EOS Germany [@PeterSvedaEOSGermany]<<
  695. 29.05.2018 10:40:07, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We have 4 days to launch.
  696.  
  697. How many dry runs can the potential ABPs commit to in those 4 days?
  698.  
  699. Is one per day achievable?
  700. 29.05.2018 10:42:13, Charles H - EOS 42 [@ankh2054]: at least one per day I would hope.
  701. 29.05.2018 10:59:58, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I'd suggest we have a schedule, Publish a list of participants who join each and capture any issues/comments/suggestions somewhere. - Do we have something like this currently??
  702. 29.05.2018 11:01:59, Roshan - EOS Authority [@telepound]: 1 per day atleast with the bios boot group. Just cautious about the 1st June code dump that might cause any breaking changes!
  703. .....29.05.2018 11:04:09, Matthew Darwin - EOS Nation [@mdarwin]: >>unsupported service message type: messageActionChatJoinedByLink<<
  704. 29.05.2018 11:08:08, Sharif Bouktila - EOS Dublin [@sharifbouktila]: That's a risk we are carrying. No way around it.
  705. 29.05.2018 11:11:14, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Just caught up on the channel here. Great leadership folks! This morning we had 60 people on the call to launch stage 16 with eos-bios. We are really looking forward to working with EVERYONE on rehearsing. Maybe the schedule we proposed isn't right. We are looking for another launch at 1300UTC tomorrow but happy to change that. Winlin is also making progress on validation. The community still needs more validation!
  706. 29.05.2018 11:11:41, Alexandre Bourget - EOS Canada [@abourget]: Hey guys, I had a suggestion for the boot sequence.. I thought we could add an eosio.burned as a system account, and send any tokens that we don't want in circulation anymore, there..
  707. 29.05.2018 11:12:09, Alexandre Bourget - EOS Canada [@abourget]: Right now, we need to issue more token to pay for RAM and delegate stuff.. but we have no recall to destroy the extra..
  708. 29.05.2018 11:12:20, Alexandre Bourget - EOS Canada [@abourget]: we could, post-launch, destroy any overflow remaining in eosio to eosio.burned
  709. 29.05.2018 11:12:21, Alexandre Bourget - EOS Canada [@abourget]: what do you think ?
  710. 29.05.2018 11:15:46, Alexandre Bourget - EOS Canada [@abourget]: FOLKS: If we don't plan for that.. it's going to backfire with a very bad signal to the holders.. We said there would be 1B tokens.. if we issued 2B.. that dilutes the whole thing.. we need a plan to destroy the excess.
  711. 29.05.2018 11:16:49, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Agreed - We need to burn excess.
  712. 29.05.2018 11:25:01, Alexandre Bourget - EOS Canada [@abourget]: I think it should be the first operation after mainnet goes live.. that someone proposed an msig `transaction to be signed by active BPs, that transfers excess EOS from `eosio to eosio.burned ... I'll add that account creation in the boot seq.
  713. 29.05.2018 11:25:02, Charles H - EOS 42 [@ankh2054]: yes definitly a good plan.
  714. 29.05.2018 11:27:31, Jae Chung - HKEOS [@jaechung]: I think this is a good idea
  715. 29.05.2018 11:27:48, Jae Chung - HKEOS [@jaechung]: @abourget does this mean we should create an extra billion (11 billion instead of 10 billion)?
  716. 29.05.2018 11:30:01, Alexandre Bourget - EOS Canada [@abourget]: hmm.. Todd is saying this will change.. (in Jungle Testnet chan).. we'll need to sync.. darn :) thought changes were over
  717. 29.05.2018 11:40:29, Alexandre Bourget - EOS Canada [@abourget]: @xebb82 and friends, might want to read the conversation in the Jungle Testnet channel.. news and decisions
  718. 29.05.2018 11:42:33, Alexandre Bourget - EOS Canada [@abourget]: It *would* have been awesome that we cap to 1B, not a coin more at start.. but the solution to this is: no producers have any account, and users buy their own RAM..
  719. 29.05.2018 16:09:33, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Guys can we agree and publish a schedule for Launch Dry Runs for the next 4 days. (Wed, Thur, Fri, Sat)
  720.  
  721. Should we have a signup sheet to see which teams are taking part each day?
  722.  
  723. Do we have a list of BPs who are willing to take part in Launch on Sunday 3rd June?
  724.  
  725. What time should we start on Sunday 3rd June? Suggesting 11:00 UTC How would that work for teams EAST and WEST ?
  726. 29.05.2018 16:28:09, David P - EOS42 [@GunnisonCap]: That’s a good idea, do you want to get a central spreadsheet up and we can build up the list. We need to ensure BPs from across Asia are fully engaged with these too and involved in the dry runs
  727. 29.05.2018 16:29:17, David P - EOS42 [@GunnisonCap]: 11am UTC works globally but frankly no time will be right for long, it seems as good as any.
  728. 29.05.2018 16:32:34, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: Yes. Great initiative guys. A spreadsheet sounds ideal.
  729. 29.05.2018 16:38:35, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Ok will we use the same spreadsheet to collect contact details (email/phone numbers) of all potential BPs? or is there another solution to that yet?
  730. 29.05.2018 16:39:55, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I suggest for these dry runs we keep it as close to production as possible - Keybase for comms etc..
  731. 29.05.2018 16:40:06, Marc-Antoine Ross - EOS Canada [@marcantoineross]: I think 1100UTC will be rough for west coast in North America. We've been running sessions at 1300UTC and it's still too early for them. Maybe 1400UTC would be a bit less worse?
  732. 29.05.2018 16:40:38, deck - EOS New York [@deckw]: anything stopping us from running two a day?
  733. 29.05.2018 16:40:55, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: Agree, 1400 UTC is fine..
  734. 29.05.2018 16:40:57, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Not on our side !
  735. 29.05.2018 16:41:10, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Would we get production like participation twice a day?
  736. 29.05.2018 16:41:32, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Yes on our side 🙂
  737. 29.05.2018 16:41:40, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: yes, we should. Training is now required..
  738. 29.05.2018 16:42:25, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Can I suggest that we keep BIOS launch group running for the ones who are training still.
  739. 29.05.2018 16:42:47, Sharif Bouktila - EOS Dublin [@sharifbouktila]: And have Production Dry Runs for the ones what have already participated ?
  740. 29.05.2018 16:44:12, Sharif Bouktila - EOS Dublin [@sharifbouktila]: i.e if you haven't done it before, take part in normal BIOS Boot , and once comfortable , "graduate" to our Production Dry Runs.
  741. 29.05.2018 16:45:48, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I'd like the production dry runs to be the same as we do on Sunday. Same Time, Same Tools, Same Phases etc..
  742. 29.05.2018 17:05:44, Sharif Bouktila - EOS Dublin [@sharifbouktila]: It's getting late here. Can someone stateside get a spreadsheet together for Production Dry Runs please. Maybe @SeanPaul19 ??
  743. .....29.05.2018 17:06:13, Matthew Bryce 马修·布赖斯 - BitSpace [@matthewbryce]: >>invited Lars Ihler - BitSpace [@LarsIhler]<<
  744. 29.05.2018 18:03:03, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: Yeah sure.
  745. 29.05.2018 20:35:02, Kyle - EOSVibes [@TheAwakenment]: 💯%
  746. 29.05.2018 21:49:23, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Nathan Rempel | GenerEOS Sydney [@nsrempel], 29.05.2018 21:45:47}}
  747. @daniellarimer curious if you have any thoughts about bps granting themselves short names during the boot process
  748. 29.05.2018 21:49:23, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 21:48:54}}
  749. they would have to get community approval for it
  750. 29.05.2018 21:49:24, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 21:48:59}}
  751. I would advise against it
  752. 29.05.2018 21:50:06, Kevin Rose - EOS New York [@eosnewyork]: That solves that mystery.
  753. 29.05.2018 21:53:05, deck - EOS New York [@deckw]: so we are creating b1b1b1b1b1b1?
  754. 29.05.2018 21:53:12, deck - EOS New York [@deckw]: :)
  755. 29.05.2018 21:55:31, Igor Lins e Silva - EOS Rio [@igorls]: +1
  756. 29.05.2018 21:56:43, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Nathan Rempel | GenerEOS Sydney [@nsrempel], 29.05.2018 21:54:21}}
  757. at the moment most boot processes seem to be making the assumption that the boot node will use eosio to create accounts for the 20 other participating producers prior to the 15% stake event
  758. 29.05.2018 21:56:43, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 21:55:48}}
  759. if they do that then they should make it 12 char names
  760. 29.05.2018 21:57:13, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 21:50:21}}
  761. it could be viewed as the initial producers taking advantage. This is why I wanted 10 liquid EOS so the initial producer canidates could buy "nice" 12 char names.
  762. 29.05.2018 21:57:14, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Nathan Rempel | GenerEOS Sydney [@nsrempel], 29.05.2018 21:52:37}}
  763. Is that 10 liquid EOS in every snapshot account?
  764. 29.05.2018 21:57:14, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 21:53:11}}
  765. assuming the account had over 11 EOS
  766. 29.05.2018 21:57:45, Nathan Rempel | GenerEOS Sydney [@nsrempel]: sent those backwards heh
  767. 29.05.2018 22:06:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 22:04:55}}
  768. I think the initial "boostrap" producers should have "throw away accounts" that people don't vote for, everyone, including the initial producers, should have to register an account and a producer by the same method.
  769.  
  770. In my boot process there would only be 1 initial producer to supervise the election, but the community seems to want 21 initial producers. Either way these initial producers should not even be registered to vote (and don't need to be registered in order to become initial producers).
  771. 29.05.2018 22:06:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 22:05:30}}
  772. the bios contract can call "setprods" to the initial 21
  773. 29.05.2018 22:06:27, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 22:05:46}}
  774. the eosio.system contract wouldn't even have producer records for them
  775. 29.05.2018 22:06:27, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 22:05:51}}
  776. thus the initial prods could not be voted for
  777. 29.05.2018 22:16:44, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Alexandre Bourget - EOS Canada [@abourget], 29.05.2018 22:14:47}}
  778. isolating the whole boot seq on a single node, makes it a *lot* faster, protects from injections, deadlines, and then swarms the blocks out..
  779. 29.05.2018 22:16:45, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 22:14:58}}
  780. I agree with this
  781. 29.05.2018 22:16:45, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 29.05.2018 22:15:18}}
  782. this is the approach I advocate
  783. 29.05.2018 22:21:58, Craig Murray - EOS BlockSmith [@craigmurray100]: oh that would be interesting... so no 21 ABPs at all
  784. 29.05.2018 22:22:14, Craig Murray - EOS BlockSmith [@craigmurray100]: just 1 guy creates a node and says "ok everyone come here and regproducer and vote" from his 1 machine
  785. 29.05.2018 22:22:16, deck - EOS New York [@deckw]: that is interesting. Seems dicey if we think there will be an attack
  786. 29.05.2018 22:22:31, Craig Murray - EOS BlockSmith [@craigmurray100]: as long as that 1 node is really durable :)
  787. 29.05.2018 22:22:38, deck - EOS New York [@deckw]: could be done with nodes in front
  788. 29.05.2018 22:22:53, Craig Murray - EOS BlockSmith [@craigmurray100]: yeah a full topology is durable
  789. 29.05.2018 22:23:02, deck - EOS New York [@deckw]: hmm...
  790. 29.05.2018 22:23:07, deck - EOS New York [@deckw]: I don't hate it
  791. 29.05.2018 22:24:02, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 1 node is easy to pause, provide validation proof, allow other connections to read the block and do simulataneous validation, then allow producers to connect and register
  792. 29.05.2018 22:24:30, deck - EOS New York [@deckw]: Would be really quick too.
  793. 29.05.2018 22:24:32, Craig Murray - EOS BlockSmith [@craigmurray100]: it makes things a lot easier
  794. 29.05.2018 22:25:24, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: have a cloudfront business plan ahead of it
  795. 29.05.2018 22:25:36, deck - EOS New York [@deckw]: './eos-bios boot --single' and put nodes in front and have at it
  796. 29.05.2018 22:25:45, Craig Murray - EOS BlockSmith [@craigmurray100]: ok, so let's have each BP launch a full topology and then submit it to everyone, and we can have 179 nodes, each one that every other BP has to then register on and we can tell all the wallet portals about the 179 nodes that are candidates
  797. 29.05.2018 22:26:01, Craig Murray - EOS BlockSmith [@craigmurray100]: <sarcasm>
  798. 29.05.2018 22:26:14, deck - EOS New York [@deckw]: Still waiting on that sarcasm font
  799. 29.05.2018 22:26:18, Craig Murray - EOS BlockSmith [@craigmurray100]: it does seem like a likely way to have multiple mainnets
  800. 29.05.2018 22:27:10, Nathan Rempel | GenerEOS Sydney [@nsrempel]: well, depends if everyone wants to be a boot or if we can agree on "one" or a small selection of boot nodes
  801. 29.05.2018 22:27:15, Nathan Rempel | GenerEOS Sydney [@nsrempel]: validate them all and choose one
  802. 29.05.2018 22:27:21, Craig Murray - EOS BlockSmith [@craigmurray100]: i guess we could all use eos-bios to create weights and the boot node just never reconnects
  803. 29.05.2018 22:27:42, Craig Murray - EOS BlockSmith [@craigmurray100]: whoever has the highest total weight we have already agreed to "support 1 mainnet"
  804. 29.05.2018 22:27:54, Craig Murray - EOS BlockSmith [@craigmurray100]: we use eos itself to form consensus on a single BP group to run the bios node
  805. 29.05.2018 22:28:07, Craig Murray - EOS BlockSmith [@craigmurray100]: we all regproducer and wait for 15%
  806. 29.05.2018 22:32:50, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: 😂
  807. 29.05.2018 22:39:06, Craig Murray - EOS BlockSmith [@craigmurray100]: I'd be looking at @igorls, @xebb82 , and @abourget as possible candidates to run the 1 boot node that gets us to 15%.
  808. 29.05.2018 22:39:56, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Yeah honestly whoever has the most experience making sure the boot and validation is accurate is what's important
  809. 29.05.2018 22:40:07, Nathan Rempel | GenerEOS Sydney [@nsrempel]: and that it wont go down once all the producers connect
  810. 29.05.2018 22:46:24, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: 1 initial producer seems to solve a lot of problems.
  811. 29.05.2018 22:51:34, Alexandre Bourget - EOS Canada [@abourget]: that's in the contract though, b1 is hardcoded in there...
  812. 29.05.2018 23:00:07, Igor Lins e Silva - EOS Rio [@igorls]: That is one single change that doesn't hurt much ;) but I'm okay with b1 too
  813. 30.05.2018 02:35:04, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: [[Webpage]]https://docs.google.com/spreadsheets/d/1wvk5eOtb8hscIWXdaVP8eED0-Ec_SKiENSX_RVgTIiA/edit?usp=sharing
  814. 30.05.2018 02:39:50, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Thanks @SeanPaul19
  815. 30.05.2018 03:29:28, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I second either one of @igorls @xebb82 @abourget to be our boot node.
  816.  
  817. I would suggest that one of them should be in each Production Dry Run.
  818.  
  819. For go-live, we need a way to pick one. Personally I'd suggest a dance off live streamed on EOS Go , but Rock Paper Scissors could work also. (or another way)
  820.  
  821. Questions:
  822.  
  823. 1. Should all Launch BPs sign something - BP agreement or similar ??
  824.  
  825. 2. Should only the ABPs be in the secure comms channel? Do we have one for everyone and then move to a smaller one with just the 21?
  826.  
  827. 3. Can we set the criteria for go-no go on Sunday. ( Validated snapshot , BPs online and checked in etc.. )
  828. .....30.05.2018 03:40:22, Boseok Kang [@boseokkang]: >>unsupported service message type: messageActionChatJoinedByLink<<
  829. 30.05.2018 03:54:17, WinLin-EOSBIXIN [@hiwinlin]: Validation Tool Progress:
  830. the functions have been realized mostly, I have test in stage16.testnets.eoscanada.com and waiting to next stage check.
  831.  
  832. Feature:
  833. Contracts validation
  834. Account privilege check
  835. Snapshot balance validation
  836. Support eos-bios BIOS and easily to DIY
  837. 30.05.2018 03:54:22, WinLin-EOSBIXIN [@hiwinlin]: [[Webpage]]https://github.com/EOSBIXIN/eostoolkit/tree/dev/eos_validator
  838. 30.05.2018 04:08:02, Eric - sw/eden [@xebb82]: I'll PM u a bit.
  839. 30.05.2018 04:44:06, Charles H - EOS 42 [@ankh2054]: +1 on @xebb82 @igorls @abourget as the possible boot nodes. Can I suggest we have a call today to go through this.
  840. .....30.05.2018 05:56:14, Tim Weston - GenerEOS (BP Sydney) [@timweston]: >>invited Ralf Weinand | GenerEOS (BP Sydney) [@RalfWei]<<
  841. 30.05.2018 07:13:10, WinLin-EOSBIXIN [@hiwinlin]: [[Webpage]]Validation Tool Progress:
  842.  
  843. add theories description in Readme
  844. find a way to make sure NO extra system account can be created
  845. https://github.com/EOSBIXIN/eostoolkit/tree/master/eos_validator
  846. 30.05.2018 07:13:14, WinLin-EOSBIXIN [@hiwinlin]: [[Photo]]
  847. .....30.05.2018 07:14:52, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>unsupported service message type: messageActionPinMessage<<
  848. 30.05.2018 07:17:55, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I have pinned the sign up sheet for the Launch Dry Runs
  849.  
  850. I suggest that on Saturday's one we aim to launch a testnet with EOS 1.0 and leave it running for an extended period. Maybe keep the SYS token name?
  851.  
  852. We need a GitHub repo not just for the code base, but also for everyone to log issues.
  853.  
  854. Any suggestions?
  855. 30.05.2018 07:58:21, Alexandre Bourget - EOS Canada [@abourget]: There's a few folks that practiced being a boot node in the other channel. They did it successfully.. eosnation, eoslaomao and a few others.
  856. 30.05.2018 08:00:41, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Is 3 not enough??
  857. 30.05.2018 08:01:37, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Personally I don't mind.
  858. 30.05.2018 08:18:25, Alexandre Bourget - EOS Canada [@abourget]: Well the eos-bios process was to let the community decide (through votes on chain). I do think they will make a fair choice.
  859.  
  860. Not sure I want to go back and say it's going to be X and Y
  861. 30.05.2018 08:20:38, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Ok so BPs opt in for Boot
  862.  
  863. Any risk some will do it incorrectly? And get picked?
  864. 30.05.2018 08:22:39, Alexandre Bourget - EOS Canada [@abourget]: always a risk, but if they do.. we just outvote them and do it 5 minutes after..
  865. 30.05.2018 08:22:46, Alexandre Bourget - EOS Canada [@abourget]: so not a big risk they screw up long-term anything
  866. 30.05.2018 08:32:53, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Apart from optics, any concern is asking teams in advance if they are putting themselves in to be bios node?
  867.  
  868. Can we ask for the same disco files for Friday and Sat dry runs ?
  869. 30.05.2018 10:51:59, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I'm assuming John Doe wasn't able to participate in a Dry Run launch today alone.
  870.  
  871. Do we think we can get a combined dry run done tomorrow ??
  872.  
  873. @abourget @igorls @xebb82 Do we work on making the BIOS launches that we have production dry runs?? How many are taking part in BIOS there today??
  874. 30.05.2018 10:55:59, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Quick update: over 70 people on the call, roughly 35 active BP accounts, @igorls meshed in as an ABP and producing. We are testing pausing the chain now just to see if it works.
  875. 30.05.2018 10:56:14, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Some of us are using production style environment
  876. 30.05.2018 10:58:01, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Ok super, so it is easier to "upgrade" what you guys are doing and formalise them into Production Dry Runs than to try start anything else.
  877. 30.05.2018 11:00:05, Marc-Antoine Ross - EOS Canada [@marcantoineross]: That's a good question... There is still a lot of training for some... Maybe saying we do a production run where everyone will be aggressively DDoS'ed as we go would be the barrier to entry
  878. 30.05.2018 11:01:01, Marc-Antoine Ross - EOS Canada [@marcantoineross]: I'd like everybody to be able to join, try, and prove they can handle it... We will be surprised I am sure
  879. 30.05.2018 11:03:35, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I'm sure we are all conscious of the time closing in here.
  880.  
  881. We need as many production dry runs as possible ( using Keybase , back up comms channels etc.. )
  882.  
  883. How many are possible??
  884. 30.05.2018 11:05:48, Eric - sw/eden [@xebb82]: We have had a couple of meetings with Alex and Marc and we have presented a possible solution for a compromise.
  885. Marc and Alex seemed positive but they have asked for more time to think about it and we are still waiting for confirmation. We have a few details we need to dig into and discuss further.
  886.  
  887. They are currently focused on launching / testing and we have been promised a follow-up meeting before Jae gets to bed today. In the mean-time we are trying to start detailing the plan for acceptance testing. Would love help there.
  888. We are hoping that we asap can announce that we have found a solution to move forward asap.
  889. 30.05.2018 11:07:01, Marc-Antoine Ross - EOS Canada [@marcantoineross]: I have not seen the chart yet Eric. Have you shared that with me?
  890. 30.05.2018 11:07:35, Eric - sw/eden [@xebb82]: We had Igor send it over, right?
  891. 30.05.2018 11:08:18, Marc-Antoine Ross - EOS Canada [@marcantoineross]: I don't see it in: Email, Telegram, Slack, WeChat, LinkedIn, Facebook... am I missing something ? 🙂
  892. 30.05.2018 11:08:45, Eric - sw/eden [@xebb82]: Shipping over what I have over telegram.
  893. 30.05.2018 11:09:24, Marc-Antoine Ross - EOS Canada [@marcantoineross]: thanks
  894. 30.05.2018 11:10:20, Eric - sw/eden [@xebb82]: Anytime.
  895. 30.05.2018 12:02:48, aza eosar [@p17er0bl3do]: mostly agree with dan comments, shouldnt be that hard to create the initial accounts with: 1st EOS staked, next 10 EOS liquid, and the rest staked
  896. 30.05.2018 12:05:45, Eric - sw/eden [@xebb82]: We are creating accounts for every eth add with >=1 EOS
  897. You mean buy ram for 1 EOS, right?
  898. 30.05.2018 12:09:56, aza eosar [@p17er0bl3do]: yes right
  899. 30.05.2018 17:59:48, Sharif Bouktila - EOS Dublin [@sharifbouktila]: How about this suggestion for Production Launch Dry Runs
  900.  
  901. @abourget - Thursday Dry Run
  902. @igorls - Friday Dry Run
  903. @xebb82 - Sat 13:00 UTC Dry Run
  904. Random among BIOS boots - Sat 16:00 Dry Run
  905.  
  906. Sunday - 13:00 UTC - Launching ...
  907. 30.05.2018 18:00:31, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Named people would be BOOT node and provide feedback / guidance for the group?
  908. 30.05.2018 18:00:55, David P - EOS42 [@GunnisonCap]: I like it a lot
  909. 30.05.2018 18:02:41, Alexandre Bourget - EOS Canada [@abourget]: We're already organizing staged launches each day.. but they are always random
  910. 30.05.2018 18:03:01, Alexandre Bourget - EOS Canada [@abourget]: The problem with Sunday 13:00 UTC is it's not 24 hours after freeze. Monday 1300 UTC is (over 24h actually)
  911. 30.05.2018 18:03:18, Alexandre Bourget - EOS Canada [@abourget]: It won't hurt to have everyone check the snapshot for issues.. and concentrate on that for a day (especially during the weekend)
  912. 30.05.2018 18:05:41, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I know that but we need to get from what you are currently running to something that is production ready.
  913.  
  914. E.g are all the BPs you are working with on Keybase ?? Is that what we are using ? We need a way to get this into a run book.
  915.  
  916. If you can think of a better way than planned dry runs which teams sign up to , then shout.
  917. 30.05.2018 18:08:00, Sharif Bouktila - EOS Dublin [@sharifbouktila]: @telepound When is the Freeze ? And when do you think we can start?
  918. 30.05.2018 18:08:37, Alexandre Bourget - EOS Canada [@abourget]: Well the announcements we've pinned in the EOSIO BIOS Boot channel have always gathered huge crowd.. It works fine I think.. And also, the whole community is on Telegram.. I might have preferred Keybase myself,.. but moving this late in the game isn't worth it I think.
  919. 30.05.2018 18:08:48, Alexandre Bourget - EOS Canada [@abourget]: I'm going to be offline for ~4h
  920. 30.05.2018 18:15:23, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Personally I don't care what tool we use, as long as everyone agrees to be on it and we have a back up plan (or two) in case it goes off line.
  921.  
  922. Anyone else got some ideas on what we should do between now and Sunday?
  923. .....30.05.2018 21:19:11, Kyunghwan Kim - EOSeoul.io [@resvera]: >>unsupported service message type: messageActionChatJoinedByLink<<
  924. .....30.05.2018 21:23:04, - eoseoul.io DS Lim [@dslim]: >>unsupported service message type: messageActionChatJoinedByLink<<
  925. .....30.05.2018 21:50:21, Sungmin Ma - EOSeoul.io [@moomooland]: >>unsupported service message type: messageActionChatJoinedByLink<<
  926. 30.05.2018 23:49:48, Kevin Rose - EOS New York [@eosnewyork]: Hey everyone, the most recent joint statement is ready to be published in BP launch group.
  927. .....31.05.2018 00:24:49, Hubert Chang-EOSeoul.io [@hjhc00]: >>unsupported service message type: messageActionChatJoinedByLink<<
  928. 31.05.2018 04:14:00, Roshan - EOS Authority [@telepound]: When is the freeze: ERC20 EOS tokens are frozen at June 2, 2018 at 21:59:59 UTC. [Each period is always 23 hours, so not sure why how some got 24 hours for the freeze?]
  929.  
  930. Snapshot start: We will probably run the final snapshot on 2nd June at 22:15 UTC. Will also put a high spec server at it. Snapshot will be published on github and we will compare it with other snapshots.
  931. We previously had a bug with snapshot where two runs were not the same. These bugs are fixed and should work as expected.
  932. cc @RohanWillAnswer
  933. 31.05.2018 04:17:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Thanks.
  934.  
  935. So Target launch Sunday 3rd June 13:00 UTC looks right to me.
  936. 31.05.2018 04:22:03, Roshan - EOS Authority [@telepound]: yes, that looks reasonable. however, i have never ran a full snapshot import with user balance & stakes etc. I hope to do that with @abourget & bios BPs group members at some point in the next few days. we are also running a full snapshot right now (#348) with the new snapshot code.
  937. 31.05.2018 04:38:56, David P - EOS42 [@GunnisonCap]: Be interested in an update on how the full snapshot goes Roshan, thanks
  938. 31.05.2018 04:40:27, Roshan - EOS Authority [@telepound]: sure will get back to this group
  939. 31.05.2018 04:40:49, David P - EOS42 [@GunnisonCap]: Great work on the ongoing snapshot analysis by the way gents
  940. 31.05.2018 04:42:22, Roshan - EOS Authority [@telepound]: thanks, we will also be testing yesterday's patch to confirm it works.
  941. 31.05.2018 05:08:05, Eric - sw/eden [@xebb82]: I would love to do that but saturday will be "heavy feature testing day" for me.
  942. We will have to spin up a lot of chains per day until then, and really start focusing on trying to test as much as possible as quickly as possible :D
  943. 31.05.2018 08:17:43, Alexandre Bourget - EOS Canada [@abourget]: Guys I wrote a small doc for those who don't want to use the eos-bios software, yet want to participate in ABPs and launch with the community around eos-bios:
  944.  
  945. https://github.com/eoscanada/eos-bios/blob/master/README.nobios.md
  946. 31.05.2018 10:45:42, Rohan - EOSauthority [@RohanWillAnswer]: Hello, did a snapshot to period 348 earlier today. It took about 2 hours with —resume flag (faster and recommended now). That’s probably the fastest. Waiting for the others to run 348 to compare and raise any issues.
  947. 31.05.2018 10:46:12, deck - EOS New York [@deckw]: [[Webpage]]348 is up here for us. https://github.com/eosnewyork/snapshots
  948. 31.05.2018 10:46:42, Rohan - EOSauthority [@RohanWillAnswer]: The genesis repository will stop being updated and will also be deleted today @sandw1ch .. The distribution collective repo is updated in case we need it..
  949. 31.05.2018 10:49:27, Rohan - EOSauthority [@RohanWillAnswer]: Did you run on the latest master branch of the genesis code?
  950. 31.05.2018 10:50:01, deck - EOS New York [@deckw]: should be yes
  951. 31.05.2018 10:52:37, Rohan - EOSauthority [@RohanWillAnswer]: Does not look like it, you still seem to be having the “$10m hack issue” unfixed EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV that key was in the burn list.. Your snapshot.csv seems to contain it..
  952. 31.05.2018 10:53:02, Rohan - EOSauthority [@RohanWillAnswer]: The good news is we have very little difference
  953. 31.05.2018 10:53:02, deck - EOS New York [@deckw]: is the distribution collective not up-to-date?
  954. 31.05.2018 10:53:18, Rohan - EOSauthority [@RohanWillAnswer]: When did you run this?
  955. 31.05.2018 10:53:22, deck - EOS New York [@deckw]: this morning
  956. 31.05.2018 10:53:41, Rohan - EOSauthority [@RohanWillAnswer]: I suspect you pulled before the final commits from @sandw1ch..
  957. 31.05.2018 10:53:42, deck - EOS New York [@deckw]: 2ish hours ago
  958. 31.05.2018 10:53:55, Rohan - EOSauthority [@RohanWillAnswer]: Maybe you just missed it? Can you try pulling again?
  959. 31.05.2018 10:53:58, deck - EOS New York [@deckw]: hmm ok will pull and run again
  960. 31.05.2018 10:54:25, Rohan - EOSauthority [@RohanWillAnswer]: The good news is the amounts match perfect! Just the keys disagree..
  961. 31.05.2018 10:58:55, Rohan - EOSauthority [@RohanWillAnswer]: Did you use —resume?
  962. 31.05.2018 11:01:30, deck - EOS New York [@deckw]: node snapshot —load_config —poll —period=350 —resume —verbose_mt —recalculate-wallets
  963. 31.05.2018 11:04:55, deck - EOS New York [@deckw]: I am now running with the version from the eosio repo instead of the collective.
  964. .....31.05.2018 11:50:31, Rohan - EOSauthority [@RohanWillAnswer]: >>invited Sandwich [@sandw1ch]<<
  965. 31.05.2018 11:52:10, Sandwich [@sandw1ch]: They are the same except a change in a readme file.
  966. 31.05.2018 11:54:27, deck - EOS New York [@deckw]: Yup as you explained in the other channel I was running with the wrong parameters.
  967. 31.05.2018 11:54:44, Sandwich [@sandw1ch]: Gotchya 👍
  968. 31.05.2018 11:54:51, Sandwich [@sandw1ch]: Just placing it here for later reference.
  969. 31.05.2018 11:55:00, Sandwich [@sandw1ch]: If anyone has questions, today is the day for them.
  970. 31.05.2018 11:55:15, deck - EOS New York [@deckw]: ok appreciate all your hard work
  971. 31.05.2018 11:55:15, Sandwich [@sandw1ch]: We can arrange a video call if you find that valuable.
  972. 31.05.2018 11:57:38, deck - EOS New York [@deckw]: I think that call would consist of RTFM honestly. I should have read the README first :)
  973. 31.05.2018 12:14:21, Rohan - EOSauthority [@RohanWillAnswer]: [[Webpage]]This is looking all good right? https://github.com/EOS-distribution-collective/genesis
  974. 31.05.2018 12:28:25, Sandwich [@sandw1ch]: Yes
  975. 31.05.2018 12:33:44, Sandwich [@sandw1ch]: I found something that could be adjusted in docs
  976. 31.05.2018 17:58:58, Eric - sw/eden [@xebb82]: Hello everyone,
  977.  
  978. We have been working on the steps for launching and validating the main net.
  979. This is the flow we believe is necessary to test critical functionality and allow token holders and opportunity to validate the chain before opening it up for voting.
  980.  
  981. Please have a look at it.
  982. I'll be going to bed really soon - but let's pick it up tomorrow and see if we can get some agreement.
  983. 31.05.2018 17:59:11, Eric - sw/eden [@xebb82]: [[Document, size 188'738 bytes]]
  984. 31.05.2018 18:36:42, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Photo]]
  985. 31.05.2018 18:37:10, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Just on Jungle chat , what happens when we get a bug??
  986. 31.05.2018 19:10:47, Roman CryptoLions [@romanskaskiw]: Also this advice:
  987. 31.05.2018 19:10:50, Roman CryptoLions [@romanskaskiw]: [[Photo]]
  988. 01.06.2018 04:01:46, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Everyone - Can you please take a walk through the validation process flow posted by @xebb82
  989.  
  990. Each block producer should be able to state to the EOS community what is the minimum scope of tests that they need to see successfully passed to open the chain up for voting.
  991.  
  992. We have issued statements that the Mainnet Launch Team will announce when the EOS community can begin voting.
  993.  
  994. We need to agree how we do this.
  995.  
  996. Massive amounts of work and professionalism has got us to today. I believe one more solid push will carry us over the line.
  997. 01.06.2018 04:06:02, Adrian - SaltBlock [@adrian_saltblock]: +1
  998. 01.06.2018 04:56:20, David P - EOS42 [@GunnisonCap]: Fully agree with this, we cannot have for example a chain being fast created by one group that completes no proper validation testing being presented as the mainnet. So we need to ensure there is collective understanding and consensus on this key point. Thanks Sharif how do you propose collating this?
  999. 01.06.2018 05:00:50, Eric - sw/eden [@xebb82]: We need to make sure that for us to be able to declare a chain a possible main net candidate we need to run validation. +1 on this.,
  1000. 01.06.2018 05:02:34, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Our snapshot tools cant even reach consensus...
  1001. 01.06.2018 05:02:40, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Up to 80 differences
  1002. 01.06.2018 05:02:58, Eric - sw/eden [@xebb82]: Nice :)
  1003. 01.06.2018 05:03:44, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Not nice at all 😞
  1004. 01.06.2018 05:04:26, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Hard to reach consensus on even a snapshot
  1005. 01.06.2018 05:04:50, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Why are the tools generating different results? Any ideas?
  1006. 01.06.2018 05:05:33, David P - EOS42 [@GunnisonCap]: The point is that nobody gets to launch a fast chain, skip validation testing and attempt to call that the mainnet. Not least that will not have global BP consensus required, so would cause a big problem. @abourget do you fully agree with this point?
  1007. 01.06.2018 05:07:35, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Even if the tools don't reach concensus ... Can they atleast say 'yes it's valid'
  1008. 01.06.2018 05:07:52, David P - EOS42 [@GunnisonCap]: Presenting a chain as the mainnet for voting and activation on the global exchanges that had fundamental functionality issues would be a huge mistake, not least us not fulfilling our duties as BPC’s at this crucial time. It would therefore be useful to ensure everybody here confirms they agree we need to complete robust validation testing - and probably what that entails.
  1009. 01.06.2018 05:08:08, David P - EOS42 [@GunnisonCap]: A good question
  1010. 01.06.2018 05:08:30, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: No there is no way to say something is valid
  1011. 01.06.2018 05:08:37, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Validation is literally a diff of all snapshots
  1012. 01.06.2018 05:08:59, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Ultimate validation would be all snapshot containing 0 differences
  1013. 01.06.2018 05:10:04, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Agreed but why is that so hard right now? Is it cause everyone is copying the snapshot at different times? Cause it's not locked yet? Or are you saying even if everyone uses the same snapshot and same chain.. they get different results
  1014. 01.06.2018 05:11:15, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Parity and snapshots work in mysterious ways
  1015. 01.06.2018 05:11:36, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: The chain we are talking about is ethereum
  1016. 01.06.2018 05:11:47, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: People running snapshots are getting different results
  1017. 01.06.2018 05:13:23, Nathan Rempel | GenerEOS Sydney [@nsrempel]: If one person takes a single snapshot off ethereum and compares it to an EOS chain they load.. how does that diff compare?
  1018. 01.06.2018 05:13:43, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: we are not at EOS loading step
  1019. 01.06.2018 05:13:52, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: you need consensus on which snapshot to use in the first place
  1020. 01.06.2018 05:14:10, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I see
  1021. 01.06.2018 05:15:51, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Once the erc-20 contract is frozen perhaps those differences will stop? Or does the parity mechanism extract the snapshot differently every time based on blockhash and other random variables. Forgive me if these are dumb questions.. j haven't had a chance to work with the parity/Genesis code yet :(
  1022. 01.06.2018 05:17:08, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Not my place to answer, perhaps @RohanWillAnswer or @igorls ?
  1023. 01.06.2018 05:19:20, Rohan - EOSauthority [@RohanWillAnswer]: We had some code updates yesterday which will hopefully make it all match correctly.. @igorls has already run the latest snapshot for period #349, I will be running it as well and we will let you know.. Fingers crossed.
  1024. 01.06.2018 05:24:53, Sharif Bouktila - EOS Dublin [@sharifbouktila]: How about this for some targets.
  1025.  
  1026. Today - 14:00 UTC - Ghostbusters Test Launch ( This should be done as close as possible to production launch as possible)
  1027. Today - 18:00 UTC - Validation Call to agree minimum testing which needs to be completed for MAINNET Launch Group to announce chain is open for voting
  1028.  
  1029. Saturday 13:00 UTC - Launch EOS 1.0 Testnet with a commitment to keep it alive for testing for 30 days.
  1030.  
  1031. My view is that all system / technical testing should happen on the 1.0 Testnet (Pre-Production) and it gives us a test bed to implement and test bug fixes before trying them in Live.
  1032.  
  1033. We need an agreed way of working. The chain will get launched , I've no doubt but without solid processes for testing and validation every bug after will be a bloody nightmare to get implemented.
  1034. 01.06.2018 05:32:27, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Sounds great
  1035. 01.06.2018 05:38:29, David P - EOS42 [@GunnisonCap]: We are pushing it 14:00 today for the testnet launch, can you find out if that needs to be pushed back an hour or two. Otherwise yes we absolutely need a call to agree minimum acceptable testing to be completed for the mainnet. Anything less is not a valid (or validated) chain.
  1036. 01.06.2018 05:39:57, Sharif Bouktila - EOS Dublin [@sharifbouktila]: The Run today is already planned by the Ghostbusters team as a practice launch. I think as many BPs as possible should take part.
  1037. 01.06.2018 05:40:04, Pete BlockMatrix [@blockmatrixpete]: Sounds like a good plan, more than happy to commit to everything mentioned here
  1038. 01.06.2018 05:41:54, David P - EOS42 [@GunnisonCap]: I know, but the call I was on at 2am I got the impression that time may need to adjust slightly so worth checking is all I’m saying.
  1039. 01.06.2018 05:42:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Ah ok - got it
  1040. 01.06.2018 05:42:32, David P - EOS42 [@GunnisonCap]: Great, to achieve our collective consensus we need more of this
  1041. 01.06.2018 05:42:56, Pete BlockMatrix [@blockmatrixpete]: 👍
  1042. 01.06.2018 05:44:13, Sharif Bouktila - EOS Dublin [@sharifbouktila]: + 1 now is not the time to stay quiet people.
  1043.  
  1044. There are millions of peoples money and reputations on the line here.
  1045.  
  1046. It is a Block Producers duty to protect the interests of Token Holders before, during and after launch
  1047. 01.06.2018 07:23:18, Alexandre Bourget - EOS Canada [@abourget]: Of course.
  1048. 01.06.2018 07:24:11, David P - EOS42 [@GunnisonCap]: Thank you, then we are all in agreement and should have no risk of an unvalidated chain being proposed as a mainnet candidate.
  1049. 01.06.2018 07:24:49, David P - EOS42 [@GunnisonCap]: Next then is confirming exactly what the validation tests required are for all chains booted to pass.
  1050. 01.06.2018 07:58:33, deck - EOS New York [@deckw]: [[Webpage]]Hey everyone I wrote up a python validation script using a 'semi-complete' python implementation of cleos. I am going to attempt to validate against both the ghostbuster testnet and eos-bios launches today. Anyone who has time please take a look or try it out for yourself. Cheers.
  1051.  
  1052. https://github.com/eosnewyork/eospy
  1053. 01.06.2018 08:26:10, Alexandre Bourget - EOS Canada [@abourget]: Folks about unregd:
  1054.  
  1055. * The unregistered_snapshot.csv now contains an account name.
  1056. * The previous proposition was to put all funds in eosio.unregd and then later create accounts and transfer tokens out of that account.
  1057. * If there is an account name now, so:
  1058. * We could create that account, just like the registered, transfer their funds on that account, and delegate its authority to eosio.unregd. In the future, that contract could do an inline transaction to set a new updateauth public key on that account, for the benefit of the person proving they own keys.
  1059.  
  1060. What do you think?
  1061. 01.06.2018 08:34:46, Adrian - SaltBlock [@adrian_saltblock]: Sounds like an extra step to validate, at a time where there's enough on the plate. Given the end result is the same, my question would be: is this really necessary right now?
  1062. 01.06.2018 08:45:42, aza eosar [@p17er0bl3do]: +1
  1063. 01.06.2018 08:50:47, WinLin-EOSBIXIN [@hiwinlin]: +1
  1064. 01.06.2018 08:53:01, WinLin-EOSBIXIN [@hiwinlin]: even we record the unregister account in the block chain, the BPs may not want to support the recovery. In other side, if the BPs want do the recovery, they can get the unregistered account in the ETH chian.
  1065. So let keep it simple.
  1066. 01.06.2018 08:53:55, WinLin-EOSBIXIN [@hiwinlin]: and make sure the mainnet is clean with the necessities
  1067. 01.06.2018 09:00:47, Ralf Weinand | GenerEOS (BP Sydney) [@RalfWei]: However if we do it at genesis, then we have a clean start and avoid inconsistencies / disputes later. We should validate this at the beginning IMO.
  1068. 01.06.2018 10:12:08, mini - EOS Argentina [@moonxor]: [[Webpage]]hey, we just push our validator with some of the scripts we used for our testnet aurora.
  1069.  
  1070. https://github.com/EOSArgentina/firestarter
  1071.  
  1072. The boot and validation (85k accounts) take 15 minutes aprox.
  1073. 01.06.2018 10:12:18, Marc-Antoine Ross - EOS Canada [@marcantoineross]: 👏
  1074. .....01.06.2018 10:39:55, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: >>invited Niclas Hedhman - EOS Germany [@niclash]<<
  1075. .....01.06.2018 19:18:11, alex k - EOS Brazil [@bakudd]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1076. 01.06.2018 19:32:41, deck - EOS New York [@deckw]: Hey everyone I appear to be missing somethign simple when I'm trying to parse the cleos get code <account> does anyone know how that hash is generated?
  1077. 01.06.2018 19:48:44, Alexandre Bourget - EOS Canada [@abourget]: Sha256 of content
  1078. 01.06.2018 19:50:24, deck - EOS New York [@deckw]: what content? wasm? wast?
  1079. 01.06.2018 20:07:50, Alexandre Bourget - EOS Canada [@abourget]: Wasm always
  1080. 01.06.2018 20:08:31, deck - EOS New York [@deckw]: ok that is what I thought.
  1081. 02.06.2018 02:43:15, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Distribution is closed.
  1082.  
  1083. EOS 1.0 is released.
  1084.  
  1085. Take a moment to think about how best we should spend our time between now and when the millions of people who are trusting us to get this done, start using our platform.
  1086.  
  1087. Focus on what is important and impactful.
  1088.  
  1089. Check your egos at the desk, you can pick them up on the other side.
  1090. 02.06.2018 02:44:24, jem [@jemxpat]: >Check your egos at the desk, you can pick them up on the other side.
  1091.  
  1092. egggsactly!
  1093. 02.06.2018 02:54:17, Eric - sw/eden [@xebb82]: 👍
  1094. 02.06.2018 03:46:10, David P - EOS42 [@GunnisonCap]: Somebody pin this 👆
  1095. 02.06.2018 03:47:43, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: 100%
  1096. 02.06.2018 03:47:49, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: The first thing we need
  1097. 02.06.2018 03:47:55, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Is consensus on validation
  1098. 02.06.2018 03:48:03, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Lets test the different external validation tools
  1099. 02.06.2018 03:48:25, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: To make sure there is some sort of consensus, otherwise there could be 3 chains, and we wouldnt even agree on which one is valid
  1100. 02.06.2018 03:49:05, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: List all the external validation tools we have so far, I know about EOSBIXIN, what else is there?
  1101. 02.06.2018 03:49:22, David P - EOS42 [@GunnisonCap]: That is indeed the priority, because consensus on validation is the first step to enabling section
  1102. 02.06.2018 03:49:35, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: And its a way to stop differences
  1103. 02.06.2018 03:49:40, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: If we have consensus on validation
  1104. 02.06.2018 03:49:43, Jae Chung - HKEOS [@jaechung]: Igor’s tool
  1105. 02.06.2018 03:50:04, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Then the first chain to launch with 15% of votes and fully verified by that consensus can be mainnet
  1106. 02.06.2018 03:50:07, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: There is no need to argue
  1107. 02.06.2018 03:50:09, Michael Yeates [@michaelyeates]: ram pricing makes validation difficult
  1108. 02.06.2018 03:50:57, Michael Yeates [@michaelyeates]: we need to work out a way to record how much was paid for ram at the time the account was created
  1109. 02.06.2018 03:51:50, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Okay, any technical solutions to this?
  1110. 02.06.2018 03:52:16, Michael Yeates [@michaelyeates]: im thinking of a couple
  1111. 02.06.2018 03:53:50, jem [@jemxpat]: I have privately asked Dan for an immediate update of the account creation RAM purchase.
  1112.  
  1113. At bios, we have a bunch of account to create. As each account requires some RAM to hold the account data, some RAM purchase must be done to allocate that RAM. With the current RAM pricing mechanism, the first user account created cost very little to allocate 8k. As we get more and more accounts, the price continuously increases, so that accounts created later cost massively more than those created earlier.
  1114.  
  1115. The variable fee makes third party account validation nearly impossible. External client queries for the account balance will show the balance minus the RAM fees, which is very, very hard to reconcile with the snapshot data, since the external probe has no ability to know the order of registration of the accounts and how the Bancor price has changed. Fixed or zero fee is the only way, it seems.
  1116.  
  1117. We suggest to B1 a code change which will make initial account creation RAM fees at bios free.
  1118. 02.06.2018 04:30:14, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: This would be a much needed fix
  1119. 02.06.2018 04:30:28, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Then we can finally do proper third party account validation
  1120. 02.06.2018 04:32:07, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Is it possible for someone in the community to make this change?
  1121. 02.06.2018 04:34:32, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: If we all have valid third party tools that multiple people can run just like the snapshot tool, then it does not matter how the chain is launched. The chain must reach the 15% threshold and have multiple BPs run the external validation tools and publically announce their results for it to be a valid chain.
  1122. 02.06.2018 04:36:12, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: So far we have validation tools from Igor, EOSBIXIN, and EOS Argentina, that can hopefully verify deterministically after the RAM costs changes occur
  1123. .....02.06.2018 04:38:44, Kyunghwan Kim - EOSeoul.io [@resvera]: >>invited Hyunwoong JI - EOSeoul.io [@EOSeoul_hyunwoong]<<
  1124. 02.06.2018 04:46:56, Sungmin Ma - EOSeoul.io [@moomooland]: I personally think Jem's opinion is valid.
  1125. Eosio thinks that Ram costs to create account should be borne by eosio, and the expense should be covered by EOSio at 4% which is left as work proposal.
  1126. And it will be a hurdle to charge new users to join the EOS ecosystem in the future, and it will not help EOS in the long run.
  1127. For a better direction, the 8kb used to create an account at EOS suggests to process the charge for free.
  1128. 02.06.2018 04:49:11, Sharif Bouktila - EOS Dublin [@sharifbouktila]: That’s right.
  1129.  
  1130. It is up to each BP to be satisfied that the chain is validated before declaring it open for staking.
  1131.  
  1132. 100% agree we need to come at this from the validating view point.
  1133. 02.06.2018 04:49:50, jem [@jemxpat]: Yes, but at this point I hope we can minimize the deviation from EOSIO. Any early changes will make ongoing synchronization slightly more difficult. Best if B1 will simply do the changes. There are multiple architectural options to accomplish it, so I would hate to have us implement it, then B1 does it later using a different approach.
  1134. 02.06.2018 04:53:46, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Agreed.
  1135.  
  1136. Could we have a pull request ready ? B.1 might accept it into their repo?
  1137.  
  1138. We are open source now.
  1139. 02.06.2018 04:53:55, jem [@jemxpat]: 나성민씨, I agree. I will ask for the change initally in the bios, then later, when we know how to create new accounts, we can use the same cost basis method.
  1140. 02.06.2018 06:01:56, Alexandre Bourget - EOS Canada [@abourget]: The way I handle this right now is that eosio buys RAM for each ERC-20 account.. at market price. For that we need to issue a bit more EOS, and we can all agree to destroy the excess by sending it to eosio.burned (an account created for that purpose) after launch.
  1141. 02.06.2018 06:02:20, Alexandre Bourget - EOS Canada [@abourget]: This way we provide 8kb RAM to everyone.
  1142. 02.06.2018 06:03:32, Michael Yeates [@michaelyeates]: i dont think we need to issue or burn, the unregistered tokens which were sent to contract addresses are highly unlikely to be reliably claimed and if they are then we have the option to issue the extra tokens needed at the time
  1143. 02.06.2018 06:04:25, Alexandre Bourget - EOS Canada [@abourget]: We have to put unreg'd money aside right now, and have that contract hold it. One or the other.. it doesn't change much in the end.
  1144. 02.06.2018 06:04:45, Alexandre Bourget - EOS Canada [@abourget]: We can inspect this morning's chain and tweak that before mainnet, still a few hours.
  1145. 02.06.2018 06:04:55, Michael Yeates [@michaelyeates]: yes, the point is that it is not good for public relations
  1146. 02.06.2018 06:05:09, Michael Yeates [@michaelyeates]: people will appear to lose tokens on the swap
  1147. 02.06.2018 06:06:34, Charles H - EOS 42 [@ankh2054]: People won’t agree with their current balances if we allow public validation.
  1148. 02.06.2018 06:07:33, Alexandre Bourget - EOS Canada [@abourget]: If eosio buys RAM, then the hodler's accounts are untouched.
  1149. 02.06.2018 06:07:39, Alexandre Bourget - EOS Canada [@abourget]: If we have hodlers pay for RAM, then what you say is true: their account won't match the new chain.
  1150. 02.06.2018 06:08:04, Charles H - EOS 42 [@ankh2054]: Aha I see :)
  1151. 02.06.2018 06:08:52, Alexandre Bourget - EOS Canada [@abourget]: I would have hoped for that collaboration weeks ago..
  1152. 02.06.2018 06:09:02, Charles H - EOS 42 [@ankh2054]: I think it’s best we avoid having users pay as those created last will also pay more.
  1153. 02.06.2018 06:09:21, Alexandre Bourget - EOS Canada [@abourget]: yes, also true, unless we buy RAM with a fixed amount of EOS.. but then not everyone gets the same amount of RAM. Those inserted last get less RAM
  1154. 02.06.2018 06:10:33, Alexandre Bourget - EOS Canada [@abourget]: A full injection of the chain, with the algorithm stated above, "invests" 19727.0815 EOS into buying RAM for its new users.
  1155. .....02.06.2018 06:10:51, Alexandre Bourget - EOS Canada [@abourget]: >>invited Daniel Larimer [@daniellarimer]<<
  1156. 02.06.2018 06:11:03, Alexandre Bourget - EOS Canada [@abourget]: @daniellarimer ^^ that risks being on chain.
  1157. 02.06.2018 06:12:49, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Let’s work from now forward.
  1158. 02.06.2018 06:13:19, Charles H - EOS 42 [@ankh2054]: Can the EOS come from all the EOS sitting in the wrong contracts?
  1159. 02.06.2018 06:14:08, Sharif Bouktila - EOS Dublin [@sharifbouktila]: No - this needs to be audit-able
  1160. 02.06.2018 06:15:40, Charles H - EOS 42 [@ankh2054]: Deduct from BP’s first month payouts? Worker proposal?
  1161. 02.06.2018 06:18:29, jem [@jemxpat]: Cleanest solution is to just set new user account RAM cost to 0. But, I really like Alex's method!
  1162. 02.06.2018 06:19:46, jem [@jemxpat]: With a 0 cost for new accounts, my only concern is that the allocated RAM might cause some unexpected interaction with the Bancor algorithm.
  1163. 02.06.2018 06:26:26, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Any reason we can't used Alex's solution for this?
  1164.  
  1165. On the call last week when it was explained, nobody saw a reason it wouldn't work.
  1166. 02.06.2018 06:27:55, Alexandre Bourget - EOS Canada [@abourget]: We have a rehearsal this morning 1300 UTC. Let's all try to validate the output.
  1167.  
  1168. We can do the exact same thing tomorrow.
  1169.  
  1170. I will whitelist contracts and freeze the chain as requested by the community.
  1171. 02.06.2018 06:29:07, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Are we going to keep today's chain alive as a testnet for an extended period ??
  1172. 02.06.2018 06:29:41, Michael Yeates [@michaelyeates]: the ghost account is the one that freezes the chain
  1173. 02.06.2018 06:29:49, Alexandre Bourget - EOS Canada [@abourget]: I don't think so.. unless people ask for it...
  1174. 02.06.2018 06:30:38, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I'm asking, do you know think its needed? A solid test net where we can test any bug fixes etc..
  1175. 02.06.2018 06:31:00, Alexandre Bourget - EOS Canada [@abourget]: Freezing can be done with -x and selectively with --contract-whitelist.
  1176.  
  1177. This morning, I'll start with -x on dissemination (start paused, so not producing).
  1178. Then slowly open up some contracts through contract-whitelist..
  1179. 02.06.2018 06:31:14, Alexandre Bourget - EOS Canada [@abourget]: and I suggest we open to all contract only when the community is ready and says "go mainnet"
  1180. 02.06.2018 06:31:44, Alexandre Bourget - EOS Canada [@abourget]: well you can always replicate that chain on your machine with a single command.. so I'm not sure we need a testnet, do we ?
  1181. 02.06.2018 06:32:15, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I thinking of a process where agreement is easier to implement when we have issues.
  1182. 02.06.2018 06:32:31, Eric - sw/eden [@xebb82]: I'm fine with that solution Alex.
  1183. We could also pay for it from the unregistered funds, and then repay that part as a worker proposal from the 4% inflation.
  1184. 02.06.2018 06:33:26, Alexandre Bourget - EOS Canada [@abourget]: Yeah.. any manipulations of the issuance can be agreed by the 21 elected.. they can propose transactions that move things around.. so I'm not so concerned about a few balances not 100% right .. provided its just a "transfer" after
  1185. 02.06.2018 06:34:19, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Agreement of 21 elected BPs is going to be a challenge for a while.
  1186. 02.06.2018 06:34:26, Alexandre Bourget - EOS Canada [@abourget]: We want snapshot absolutely right, but eosio.burned and eosio balances can fluctuate a bit
  1187. 02.06.2018 06:34:51, Alexandre Bourget - EOS Canada [@abourget]: But those funds can't move anyway.. it's just a question of perception of the maximum supply and perceived dilution.
  1188. 02.06.2018 06:35:14, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I've no issue with the approach re: funding
  1189. 02.06.2018 06:40:30, Kyunghwan Kim - EOSeoul.io [@resvera]: RAM balance of bancor is initialized once by int64_t(_gstate.free_ram()) and changed via setram action when RAM capacity is increased. If with a 0 cost for new accounts and used bytes of RAM for new accounts are removed from RAM balance(base.balance.amount) correctly, there is no side effect. Price of next 'normal' RAM buy or sell will just increase as expected(Bancor way).
  1190. 02.06.2018 06:43:02, Alexandre Bourget - EOS Canada [@abourget]: do you mean from the eosio.ram account ?
  1191. 02.06.2018 06:43:37, Alexandre Bourget - EOS Canada [@abourget]: so moving the 19k EOS from eosio.ram to eosio.burned for example, would make price start again ?
  1192. 02.06.2018 06:43:39, Alexandre Bourget - EOS Canada [@abourget]: Let me try that.
  1193. 02.06.2018 06:48:26, Kyunghwan Kim - EOSeoul.io [@resvera]: I mean rammarket initialization on system_contract constructor in eosio.system.cpp. It’s fundamental bancor system, not balance of eosio.ram account.
  1194. 02.06.2018 06:48:48, Alexandre Bourget - EOS Canada [@abourget]: Right, so no real way to "reset" that, or is there ?
  1195. 02.06.2018 06:50:39, Alexandre Bourget - EOS Canada [@abourget]: no, from what I can read.. that's set in stone.. so we'll handle the excess post-launch
  1196. 02.06.2018 06:54:37, Alexandre Bourget - EOS Canada [@abourget]: SOMETHING WE NEED:
  1197.  
  1198. we need someone to take the ricardian contracts and stuff them into the .abi files from the eos-mainnet and publish that.
  1199.  
  1200. Who's going to jump on that ?
  1201. 02.06.2018 07:08:56, Kyunghwan Kim - EOSeoul.io [@resvera]: Price of RAM is only determined by bancor balance of RAM. So to implement “with 0 cost and 0 fee” RAM for newaccount, we need another buyram and sellram action just for newaccount. Maybe ‘allocNewAccountRAM’? Its argument should be with not EOS but with required RAM amount. If RAM used by newaccount creation is regarded like ‘total_ram_bytes_reserved’ and is removed from bancor RAM balance, it seems okay without paying EOS.
  1202. 02.06.2018 07:20:32, Kevin Rose - EOS New York [@eosnewyork]: [[Webpage]]I’ve missed a lot of messages but here’s one Buddy made. https://github.com/eosnewyork/eospy
  1203. 02.06.2018 07:22:35, deck - EOS New York [@deckw]: This makes an assumption about rambuying that has changed since made. I'm updating now.
  1204. 02.06.2018 07:23:07, David P - EOS42 [@GunnisonCap]: There is no scope for 0 cost 0 fee allocNewAccountRAM being abused in the future is there? Presumably this is a restricted function proposal just for the mainnet boot?
  1205. 02.06.2018 07:27:04, jem [@jemxpat]: I think it could be used to onboard unregistered token holders post launch, if we want.
  1206. 02.06.2018 07:28:16, Kevin Rose - EOS New York [@eosnewyork]: Thanks Buddy.
  1207. 02.06.2018 07:28:16, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Okay we have @igorls , @deckw , @moonxor and EOSBIXIN’s tools
  1208. 02.06.2018 07:28:25, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: thats four external validators
  1209. 02.06.2018 07:28:29, Kevin Rose - EOS New York [@eosnewyork]: @syed_jafri
  1210. 02.06.2018 07:28:59, David P - EOS42 [@GunnisonCap]: That’s fair, just want to ensure we do not open a back door to potential RAM abuse
  1211. 02.06.2018 07:34:30, Kyunghwan Kim - EOSeoul.io [@resvera]: I don’t have specific position on that func. If consensus made, eosio.system can be updated as intended.
  1212. 02.06.2018 07:40:10, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]We've started a Document with the features which have been released in 1.0 which we believe need validation testing before we can propose a chain for mainnet
  1213.  
  1214.  
  1215. https://docs.google.com/document/d/1Bsi1__u7U4Jvl9JAomdtWu7U0DaWGPcmD9FIAzL_pQM/edit#heading=h.qtvfems4zceg
  1216. 02.06.2018 07:41:21, Sharif Bouktila - EOS Dublin [@sharifbouktila]: The Main one I see is White/Black Listing of smart contracts. We think this is essential to stop a contract if it had issues.
  1217.  
  1218. This was a principle promise which EOS made to the community.
  1219. 02.06.2018 07:54:42, Alexandre Bourget - EOS Canada [@abourget]: I'm going to try that today in the launch, start with production paused. Seed the other nodes. THen restart with contract-whitelist one by one..
  1220. 02.06.2018 07:55:23, David P - EOS42 [@GunnisonCap]: Excellent work Sharif, we’ll take a look asap
  1221. 02.06.2018 07:56:43, Michael Yeates [@michaelyeates]: this method would need 21/21 approval. in practice it would be easier to null the code
  1222. 02.06.2018 07:57:10, Alexandre Bourget - EOS Canada [@abourget]: During ABP period, it's only the ABPs... so potentially a single person.
  1223. 02.06.2018 07:57:43, Sharif Bouktila - EOS Dublin [@sharifbouktila]: How many BPs would need to agree to that ? After go-live I'm talking. Say in 60 days when a dAPP goes rouge.
  1224. 02.06.2018 07:58:32, Michael Yeates [@michaelyeates]: 15/21
  1225. 02.06.2018 07:59:07, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Should be nice and easy then, considering how well we are all working together. 🙂
  1226. 02.06.2018 07:59:54, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Also , we don't believe there is any way for an Arbitrator to be called , so we need an offline interface established.
  1227. 02.06.2018 08:01:52, Alexandre Bourget - EOS Canada [@abourget]: The whitelisting doesn't send a signal to the network.. it merely ignores transactions from the blocks produced locally.. so 15/21 doesn't cut it.. You would need all producers to sync on that
  1228. 02.06.2018 08:33:43, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Does anyone else think this is a problem?
  1229.  
  1230. After Mainnet we will have BPs (which probably haven't been involved in the launch at all) and we haven't yet agreed how they should contact each other.
  1231.  
  1232. Let alone make a decision on when and how to stop a contract.
  1233.  
  1234. Regardless of how this weekend goes, we need to think about how things get done after launch.
  1235. 02.06.2018 08:45:38, Michael Yeates [@michaelyeates]: has anyone fun a full validation on the token balances from yesterdays ghostbusters launch?
  1236. 02.06.2018 08:54:49, deck - EOS New York [@deckw]: I have not. Doing local tests I went through all the accounts in ~10 minutes. Over the network it slows dramatically.
  1237. 02.06.2018 08:54:57, deck - EOS New York [@deckw]: Working on speed ups now
  1238. 02.06.2018 09:18:05, Eric - sw/eden [@xebb82]: If you sync a node you should do it quickly, right?
  1239. 02.06.2018 09:18:24, deck - EOS New York [@deckw]: Yes sir.
  1240. 02.06.2018 09:18:34, deck - EOS New York [@deckw]: give me the endpoints!!!
  1241. 02.06.2018 09:20:12, Eric - sw/eden [@xebb82]: @michaelyeates u have one open, right?
  1242. 02.06.2018 09:24:23, deck - EOS New York [@deckw]: Tried connecting to this address that I was given: 54.229.241.156:19876 and tried the snapshot @michaelyeates gave me but had issues with the database:
  1243.  
  1244. `Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
  1245. std::exception::what: database created by a different compiler, build, boost version, or operating system`
  1246.  
  1247. I didn't want to pester so I started working on my end
  1248. 02.06.2018 09:25:18, Eric - sw/eden [@xebb82]: oh, what was in that snapshot?
  1249. 02.06.2018 09:25:36, Eric - sw/eden [@xebb82]: Looks like u got the state as well?
  1250. 02.06.2018 09:25:56, Eric - sw/eden [@xebb82]: rm -r data-dir/state
  1251. Then restart nodeos with —replay-blockchain
  1252. 02.06.2018 09:28:36, deck - EOS New York [@deckw]: same error with state dir removed
  1253. 02.06.2018 09:30:19, Eric - sw/eden [@xebb82]: ok, then remove everything in data-dir and just sync all blocks, shouldn't take any time anyways..
  1254. 02.06.2018 09:31:39, deck - EOS New York [@deckw]: I think @michaelyeates has me blocked.
  1255.  
  1256. 1867630ms thread-0 net_plugin.cpp:1954 operator() ] connection failed to 54.229.241.156:19876: Connection refused
  1257. 02.06.2018 09:31:48, deck - EOS New York [@deckw]: or whoever that is
  1258. 02.06.2018 09:52:10, deck - EOS New York [@deckw]: @xebb82 and whoever want to know. Through first 10000 accounts there are 188 errors ( this includes b1)
  1259. 02.06.2018 09:54:54, deck - EOS New York [@deckw]: https://d3ck.keybase.pub/gb_bad_accounts.txt
  1260. 02.06.2018 09:55:08, deck - EOS New York [@deckw]: some formatting issues there
  1261. 02.06.2018 10:20:57, deck - EOS New York [@deckw]: Hmm this may be my issue.
  1262. 02.06.2018 10:21:48, deck - EOS New York [@deckw]: It looks like if there is less than 10 EOS in the account you guys stake all of it?
  1263. 02.06.2018 10:24:12, Pete BlockMatrix [@blockmatrixpete]: [[Webpage]]im pretty sure that this was the logic applied: https://t.me/jungletestnet/25344 - and the code interpretation is here: https://github.com/CryptoLions/EOS-ERC20-Distribution/blob/master/drop.sh
  1264. 02.06.2018 10:25:37, deck - EOS New York [@deckw]: great that makes sense to what I just worked through.
  1265. 02.06.2018 10:26:00, Pete BlockMatrix [@blockmatrixpete]: sweet 👍
  1266. 02.06.2018 10:46:11, Eric - sw/eden [@xebb82]: We used Bohdans script.. It treats it differently if there's > or < 10
  1267. 02.06.2018 10:47:03, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: [[Webpage]]it works according to that answer: https://t.me/jungletestnet/25344
  1268. 02.06.2018 10:47:52, deck - EOS New York [@deckw]: Yup thanks guys @BohdanCryptoLions @xebb82 . I have one fix and then I should have some good things for you
  1269. 02.06.2018 10:48:38, Eric - sw/eden [@xebb82]: Great work deck! :D
  1270. 02.06.2018 10:48:55, Hyunwoong JI - EOSeoul.io [@EOSeoul_hyunwoong]: When it comes to initial 8 kb ram allocation for every account, there could be two possible ways to solve it.
  1271.  
  1272. 1. Suggestion by Alex : Issue more EOS to buy all the RAM for every account and destroy the excess.
  1273. 2. Calculate all the RAM which is needed to create all the account and remove the amount from initial balance of the Bancor contract.
  1274. The two methods are similar but as a result, the following differences exist.
  1275. Method 1 will increase the EOS balance of the Bancor contract and Method 2 will not. This is a matter of choice. We will implement method 2 just in case.
  1276. 02.06.2018 10:55:00, jem [@jemxpat]: 👍
  1277. .....02.06.2018 11:04:28, Roman CryptoLions [@romanskaskiw]: >>invited Sudip 🦁 [@JTF420]<<
  1278. .....02.06.2018 11:08:42, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>unsupported service message type: messageActionPinMessage<<
  1279. 02.06.2018 11:35:39, Hyunwoong JI - EOSeoul.io [@EOSeoul_hyunwoong]: or combined one. after processing method of Alex, remove added EOS from balance of Bancor contract.
  1280. 02.06.2018 11:52:06, mini - EOS Argentina [@moonxor]: Anyone tried firestarter validation?
  1281. 02.06.2018 12:05:33, deck - EOS New York [@deckw]: @BohdanCryptoLions @xebb82 I haven't run a full run yet but it looks like there is an issue with accounts that hold 2 EOS.
  1282. 02.06.2018 12:06:08, deck - EOS New York [@deckw]: It looks like they have staked the .90 and bought ram for .1 but they do not have a balance of EOS. Maybe I'm missing something
  1283. 02.06.2018 12:40:09, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: For all RAM 0.1 EOS
  1284. 2 EOS <= 11 EOS :
  1285. STAKE_NET "0.4500 EOS"
  1286. STAKE_CPU "0.4500 EOS"
  1287.  
  1288. TRANSFER=$(($EOS-1)) = 1 EOS
  1289. 02.06.2018 12:50:14, deck - EOS New York [@deckw]: yea but that doesn't look like what happened on chain. For example account : ha4timzqgage
  1290.  
  1291. cleos get account ha4timzqgage
  1292. shows that they have the .45 cpu and .45 net staked.
  1293.  
  1294. now cleos get currency balance eosio.token ha4timzqgage EOS should return 1.0000 EOS however it simply returns nothing.
  1295. 02.06.2018 12:56:35, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Has anyone got a page ready where we will be able to allow Users (outside world) to query their balances on EOS Mainnet candidate?
  1296. 02.06.2018 13:03:38, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: In this case probable went something wrong.. @igorls please check logs.
  1297. 02.06.2018 13:06:17, deck - EOS New York [@deckw]: It is weird that most of the failures I saw happened with accounts with 2 EOS. Just worth noting. Full logs to come
  1298. 02.06.2018 13:07:20, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: can you give some account examples? I'll check in Jungles
  1299. 02.06.2018 13:07:29, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: after I will do a drop
  1300. 02.06.2018 13:08:59, deck - EOS New York [@deckw]: yes sir
  1301. 02.06.2018 13:10:50, deck - EOS New York [@deckw]: gi4tcnqgenes
  1302. gm2danygenes
  1303. gqydqoagenes
  1304. gq3tonqgenes
  1305. gy3tonygenes
  1306. ha3dsmqgenes
  1307. he4tqnqgenes
  1308. gezdonrsgene
  1309. geztcnzugene
  1310. ge2tknbvgene
  1311. ge4dmmjzgene
  1312. gi3domrxgene
  1313. gi3tcmzygene
  1314. gmytqmjrgene
  1315. gm2tgmrvgene
  1316. gm3tonzugene
  1317. gm4tembqgene
  1318. gm4tqnrtgene
  1319. gm4tqnrtgene
  1320. gqytaobrgene
  1321. gqytimrqgene
  1322. gq2tgnbqgene
  1323. gq3tcnrrgene
  1324. guydamrtgene
  1325. 02.06.2018 13:11:59, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: thanks.. I am prepering to drop right now, so in 1-2 h we can check this
  1326. 02.06.2018 13:15:58, Daniel Larimer [@daniellarimer]: What key are you associated with B1
  1327. 02.06.2018 13:16:04, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: checking distribution:
  1328. gi4tcnqgenes 1.0000
  1329. gm2danygenes 1.0000
  1330. gqydqoagenes 1.0000
  1331. 02.06.2018 13:16:27, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: "0x00000000000000000000000000000000000000b1","b1","EOS5cujNHGMYZZ2tgByyNEUaoPLFhZVmGXbZc9BLJeQkKZFqGYEiQ","100000000.0100"
  1332. 02.06.2018 13:17:19, Daniel Larimer [@daniellarimer]: I’ll double triple check this in a bit.
  1333. 02.06.2018 13:20:48, Sharif Bouktila - EOS Dublin [@sharifbouktila]: @daniellarimer any thoughts on the checks we should do to validate the chain before releasing it?
  1334. 02.06.2018 13:22:19, Sandwich [@sandw1ch]: That's been checked after every release.
  1335. 02.06.2018 14:19:45, mini - EOS Argentina [@moonxor]: hey I was checking the the mainnet repo, it would be nice to manage it like the bitcoin repo, where you rebase periodically and your commits are always on top of the latest block one release
  1336. 02.06.2018 14:24:32, deck - EOS New York [@deckw]: Can I get the snapshot you are using so I can confirm I am using the right one
  1337. 02.06.2018 14:29:12, mini - EOS Argentina [@moonxor]: [[Webpage]]https://github.com/EOS-Mainnet/eos/commit/a416db018c043958671b80f0b70b9d0b85c8075b due to cache , this wouldnt work if you already build with core symbole name sys. it would be better to just set the coresymbole name without the if.
  1338. 02.06.2018 14:38:52, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Guys,
  1339.  
  1340. We only have 2 things to be concerned about now.
  1341.  
  1342. 1. Validation Plan - Which as a BP we want executed to declare MainNet
  1343. 2. Time of Mainnet Launch - eg. 13:00 UTC tomorrow.
  1344.  
  1345. I have pinned a Google Document to this and some people have added some suggestions.
  1346.  
  1347. We should work to have develop it into a test plan and also agree a way for people to report issues to a core group to check/escalate.
  1348.  
  1349. I know lots of people are feeling the pressure at the moment.
  1350.  
  1351. If you are tired take some rest.
  1352.  
  1353. If you have questions or concerns please share them.
  1354.  
  1355. I've no doubt that we will get this chain launched and validated soon.
  1356.  
  1357. We need to self organise and focus on only what is critical.
  1358. 02.06.2018 14:44:05, Kyunghwan Kim - EOSeoul.io [@resvera]: [[Webpage]]Implemented 'mitigatebiosramcost' action just in case, but not tested. This is combined approach of @EOSeoul_hyunwoong . It only adjusts EOS balance of Bancor when using 'mitigatebiosramcost' action with EOS used for new account. And it can be called only once.
  1359.  
  1360. https://gist.github.com/redjade/c22b2d7fcab068af67c0de31724eb710
  1361. 02.06.2018 14:45:47, Hyunwoong JI - EOSeoul.io [@EOSeoul_hyunwoong]: 👍
  1362. 02.06.2018 15:20:27, Marc-Antoine Ross - EOS Canada [@marcantoineross]: 👏
  1363. 02.06.2018 15:32:29, mini - EOS Argentina [@moonxor]: We are adding more validations, but we don't know if there Is consensus about the following.
  1364.  
  1365. 1- Token distribución: how much Is liquid, how much for CPU and how much for net,
  1366.  
  1367. 2- RAM, Is going to be 64? This should be validated
  1368. 3- max supply, 50billons?
  1369. 4- what would happend with the remaining EOS that eosio would have, should we send them to the workers fund account or should eosio keep them?
  1370. .....02.06.2018 15:33:02, Ross - Cypherglass [@Ross_Cypherglass]: >>invited Leo Ribeiro [@leordev]<<
  1371. 02.06.2018 15:35:43, Patryk @perduta from Tokenika [@perduta]: i think we should burn them, but that's only a opinion
  1372. 02.06.2018 15:46:03, mini - EOS Argentina [@moonxor]: The eosio.token contract can't burn tokens :(
  1373. 02.06.2018 15:47:06, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: you can send it to EOS1111111111111111111111111111111114T1Anm
  1374. 02.06.2018 15:48:32, mini - EOS Argentina [@moonxor]: You can't Transfer to an address
  1375. 02.06.2018 15:49:09, mini - EOS Argentina [@moonxor]: You csn Transfer to an account with no authorities
  1376. 02.06.2018 15:49:33, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: 👍
  1377. 02.06.2018 15:49:53, mini - EOS Argentina [@moonxor]: You were saying that?
  1378. 02.06.2018 15:50:36, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: you are right.. but I didnt try that... or create account with that address
  1379. 02.06.2018 15:59:30, mini - EOS Argentina [@moonxor]: I think what would work Is: 1-50/50 for distribution,
  1380. 2 ram 64gb,
  1381. 3 50B of max supply,
  1382. 4- we send Any remainings to the workers fund.
  1383.  
  1384. But this should be put to consensus
  1385. 02.06.2018 16:01:00, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I am fine with this, lets get everyone else writing a validation tool to agree to this
  1386. 02.06.2018 16:01:10, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: @deckw @igorls
  1387. 02.06.2018 16:01:19, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: anyone have the telegram for EOSBIXIN? they should be in here
  1388. 02.06.2018 16:03:58, deck - EOS New York [@deckw]: sounds good. @abourget to ensure 50B is the max supply. I think he set it to 10B
  1389. 02.06.2018 17:39:18, Alexandre Bourget - EOS Canada [@abourget]: According to my calculation, with 5% inflation yearly, 10B is largely enough..
  1390. 02.06.2018 17:39:24, Alexandre Bourget - EOS Canada [@abourget]: Do you have a reason to put 50B there ?
  1391. 02.06.2018 17:39:41, Alexandre Bourget - EOS Canada [@abourget]: in 10 years.. we can probably tweak the contract to tweak that number a bit..
  1392. 02.06.2018 17:42:04, Alexandre Bourget - EOS Canada [@abourget]: @xebb82 @jemxpat tested the "contract-whitelist".. and it works well. you can stop any action from going through.
  1393. 02.06.2018 17:42:07, mini - EOS Argentina [@moonxor]: 10B sounds fair, 50B was a more of "just in case"
  1394. 02.06.2018 17:42:24, Alexandre Bourget - EOS Canada [@abourget]: we can tweak that later
  1395. 02.06.2018 18:40:37, Alexandre Bourget - EOS Canada [@abourget]: EVERYONE:
  1396.  
  1397. Please run any validation on chain: stage20.eb.infra.eosamsterdam.net:9876
  1398.  
  1399. It uses snapshot 350/0.. see pinned message on the EOSIO BIOS Boot channel
  1400. 02.06.2018 19:11:32, mini - EOS Argentina [@moonxor]: [[Webpage]]hey, more info about our validation tool
  1401.  
  1402. https://steemit.com/@eosargentina/firestarter-boot-and-validation-tool
  1403. 02.06.2018 19:32:09, mini - EOS Argentina [@moonxor]: hey would love to, do you have a block where you know for sure that eosio has resigned?
  1404. 02.06.2018 19:47:48, Marc-Antoine Ross - EOS Canada [@marcantoineross]: From Alex:
  1405. TO ALL:
  1406.  
  1407. * Validation succeeded 696158/696158, took 28 minutes to inject full snapshot. 350/0
  1408. * I updated https://abourget.keybase.pub/stage20/genesis.json .. RESET YOUR CHAIN with that genesis.json and execute meshing like you did this morning..
  1409. * Genesis public key: EOS6QbvV1pE9UdxbozZVPPiNyFTrvUZCnohpEYpib8jKUKyy7r1sA
  1410. * Resignation block: 3189
  1411. * Chain ID: 51b4f3b0800c7af8c4f2ce5d5038517b7090cecc0b7e63b8d6cab079038a8568
  1412. 02.06.2018 19:49:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Was this a dry run validation? Just to clarify
  1413. 02.06.2018 19:51:04, Marc-Antoine Ross - EOS Canada [@marcantoineross]: full snapshot. 350/0 so before the contract freeze
  1414. .....02.06.2018 19:52:00, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>invited Denis | EOS Nation [@DenisCarriere]<<
  1415. 02.06.2018 19:52:19, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: not the final version
  1416. 02.06.2018 19:52:43, Rohan - EOSauthority [@RohanWillAnswer]: I missed this group..
  1417. 02.06.2018 19:52:47, Marc-Antoine Ross - EOS Canada [@marcantoineross]: @RohanWillAnswer @DenisCarriere How's the snapshot consensus going?
  1418. 02.06.2018 19:52:51, Rohan - EOSauthority [@RohanWillAnswer]: [[Webpage]]Here is the final snapshot v1 on the EOS Authority repo
  1419. https://github.com/eosauthority/genesis/tree/master/snapshot-files/final/1
  1420. 02.06.2018 19:53:13, Rohan - EOSauthority [@RohanWillAnswer]: I didn’t get a chance to compare with anyone else. I’ve had another machine and it was a perfect match!
  1421. 02.06.2018 19:53:13, Marc-Antoine Ross - EOS Canada [@marcantoineross]: can you please PR eos-bios?
  1422. 02.06.2018 19:54:26, Rohan - EOSauthority [@RohanWillAnswer]: I just know of @igorls and @deckw who are nearly there.. Also I suspect others are close..
  1423. 02.06.2018 19:55:00, mini - EOS Argentina [@moonxor]: Awesome!
  1424. 02.06.2018 19:55:31, Marc-Antoine Ross - EOS Canada [@marcantoineross]: let us know how the validation goes please
  1425. 02.06.2018 19:58:58, Alexandre Bourget - EOS Canada [@abourget]: Around 3479.. there's no transactions in blocks after that for the most part.
  1426. 02.06.2018 19:59:17, Alexandre Bourget - EOS Canada [@abourget]: Check the output.log on keybase (same dir as the genesis.json)
  1427. 02.06.2018 20:12:06, Denis | EOS Nation [@DenisCarriere]: @abourget I'm syncing to @monetashi 's endpoint and for some reason when I query eosio there's a very large balance left over:
  1428.  
  1429. $ cleos get currency balance eosio.token eosio
  1430. 1560977134.1908 EOS
  1431.  
  1432. Also when I try to query my own accounts, none of them are present in the chain.
  1433.  
  1434. I'm using chain_id => 51b4f3b0800c7af8c4f2ce5d5038517b7090cecc0b7e63b8d6cab079038a8568
  1435. 02.06.2018 20:14:28, deck - EOS New York [@deckw]: can someone confirm their nodeos --version output for 1.0.1?
  1436. 02.06.2018 20:14:46, Nathan Rempel | GenerEOS Sydney [@nsrempel]: nodeos —version
  1437. 157394272
  1438. 02.06.2018 20:14:50, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: 157394272
  1439. 02.06.2018 20:14:56, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: thats right off of eosio branch
  1440. 02.06.2018 20:14:57, deck - EOS New York [@deckw]: ok cool thank you guys
  1441. 02.06.2018 20:39:08, mini - EOS Argentina [@moonxor]: just finish a team meating, sorry for the delay.
  1442. 02.06.2018 20:43:01, mini - EOS Argentina [@moonxor]: [[Webpage]]so, I just added validation criteria inside the google doc that @sharifbouktila posted.
  1443.  
  1444. I think we should divide that in 2 areas, one is software testing(unit testing), wich i think most of them are already in block one unit test, and then the validation criteria for the chain.
  1445.  
  1446. https://docs.google.com/document/d/1Bsi1__u7U4Jvl9JAomdtWu7U0DaWGPcmD9FIAzL_pQM/edit#
  1447.  
  1448.  
  1449. We already added most of this validation to firestarter, and we are working on adding the rest
  1450. 02.06.2018 20:46:54, mini - EOS Argentina [@moonxor]: it would be awesome if we can reach consensus and made a joint statement about chain validation params.
  1451. 02.06.2018 20:53:58, mini - EOS Argentina [@moonxor]: @marcantoineross @abourget
  1452. http://stage20.eb.infra.eosamsterdam.net:9876/v1/chain/get_info
  1453. 02.06.2018 20:54:48, Dafeng Guo - EOS Asia [@dftle]: 👍
  1454. 02.06.2018 20:56:55, mini - EOS Argentina [@moonxor]: need a p2p endpoint to validate
  1455. 02.06.2018 20:58:00, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: try ours
  1456. 02.06.2018 20:58:07, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: fullnode.eoslaomao.com:443
  1457. 02.06.2018 20:58:35, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: +1
  1458. 02.06.2018 20:59:45, mini - EOS Argentina [@moonxor]: same block?
  1459. 02.06.2018 21:12:21, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Update on snapshots guys?
  1460. 02.06.2018 21:30:16, Tim Weston - GenerEOS (BP Sydney) [@timweston]: @unlockrs Do we have a generic announcment for when the cahin is enabled and can announce its ready to vote on
  1461. 02.06.2018 21:35:27, mini - EOS Argentina [@moonxor]: [[Photo]]
  1462. 02.06.2018 21:36:41, mini - EOS Argentina [@moonxor]: we skip the genesis validation, and we found this
  1463. 02.06.2018 21:36:48, mini - EOS Argentina [@moonxor]: [[Photo]]
  1464. 02.06.2018 21:36:53, Rick Schlesinger - EOS New York [@unlockrs]: @eosnewyork
  1465. .....02.06.2018 21:36:55, Chitty 🅑 - EOS Argentina [@JChitty]: >>invited Sebastian Castro - EOS Argentina 🇦🇷 [@sebicas]<<
  1466. 02.06.2018 21:39:56, Chitty 🅑 - EOS Argentina [@JChitty]: that means that the owner and the active authorities are controlled by a key instead of the eosio account
  1467. 02.06.2018 21:41:13, Dafeng Guo - EOS Asia [@dftle]: @moonxor that's the report for @zhaoyu 's endpoint?
  1468. 02.06.2018 21:41:22, mini - EOS Argentina [@moonxor]: yes, is the only one i have
  1469. 02.06.2018 21:43:13, Dafeng Guo - EOS Asia [@dftle]: @abourget @zhaoyu check the screenshot above, is this a version issue?
  1470. 02.06.2018 21:46:27, WinLin-EOSBIXIN [@hiwinlin]: inital_timestamp not equal? but I check the picture and they are the same
  1471. 02.06.2018 21:47:05, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: hahah
  1472. 02.06.2018 21:47:05, deck - EOS New York [@deckw]: missing .000
  1473. 02.06.2018 21:47:11, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: this
  1474. 02.06.2018 21:47:16, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: different significance
  1475. 02.06.2018 21:47:47, mini - EOS Argentina [@moonxor]: The first one Is extracted, from the blockchain, the second one Is the one you use
  1476. 02.06.2018 21:47:54, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: eosio.ramfree fail verification?
  1477. 02.06.2018 21:49:11, Chitty 🅑 - EOS Argentina [@JChitty]: yes
  1478. 02.06.2018 21:49:48, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: eosio.ramfree not resigned, correct?
  1479. 02.06.2018 21:50:28, mini - EOS Argentina [@moonxor]: @syed_jafri
  1480. .....02.06.2018 21:51:05, Chitty 🅑 - EOS Argentina [@JChitty]: >>invited Gustavo Mick - EOS Argentina [@gustavomick]<<
  1481. 02.06.2018 21:52:10, mini - EOS Argentina [@moonxor]: Yes the screenshot says that
  1482. 02.06.2018 21:56:56, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: @abourget update the genesis in your new chain
  1483. 02.06.2018 22:10:57, Alexandre Bourget - EOS Canada [@abourget]: the latest genesis was from ~4h ago.. I haven't started another one after that..
  1484. 02.06.2018 22:52:39, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: {{FWD: WinLin-EOSBIXIN [@hiwinlin], 02.06.2018 22:51:35}}
  1485. [[Photo]]
  1486. 02.06.2018 22:52:58, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: {{FWD: WinLin-EOSBIXIN [@hiwinlin], 02.06.2018 22:51:56}}
  1487. I have successed to validation the eos-bios boot --signal 👏
  1488. 02.06.2018 22:54:03, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Looks like there is *some* post-chain validation consensus between 2 tools, we need more though
  1489. 02.06.2018 22:56:46, mini - EOS Argentina [@moonxor]: so @abourget @zhaoyu did you use this snapshot?
  1490. https://raw.githubusercontent.com/eoscanada/eos-bios/master/files/snapshot.csv
  1491. 02.06.2018 22:58:06, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]the one listed here: https://github.com/eoscanada/eos-bios/blob/master/sample_config/my_discovery_file.yaml
  1492. 02.06.2018 22:58:26, Marc-Antoine Ross - EOS Canada [@marcantoineross]: That is the one we are pushing now (shortly)
  1493. 02.06.2018 22:58:50, Alexandre Bourget - EOS Canada [@abourget]: no sorry. that's old.. I'm using EOS Authority,s snapshots right now.
  1494.  
  1495. I took them out
  1496. 02.06.2018 22:59:57, Nathan Rempel | GenerEOS Sydney [@nsrempel]: stage20 doesn't have my erc-20 account :(
  1497. 02.06.2018 23:00:04, Sebastian Castro - EOS Argentina 🇦🇷 [@sebicas]: [[Webpage]]https://github.com/eosauthority/genesis/tree/master/snapshot-files/final/1
  1498. 02.06.2018 23:00:43, mini - EOS Argentina [@moonxor]: Ok great thanks
  1499. 02.06.2018 23:02:01, Alexandre Bourget - EOS Canada [@abourget]: the chain was forked :) we were testing handoff of ABP, and the person doing the handoff forked the chain..
  1500. 02.06.2018 23:02:07, Alexandre Bourget - EOS Canada [@abourget]: I'm about to push a new genesis.json :)
  1501. 02.06.2018 23:02:22, Nathan Rempel | GenerEOS Sydney [@nsrempel]: hahaha
  1502. 02.06.2018 23:03:09, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Confirmation from eosDAC, EOS Authority and Cryptolions on snapshots matching up!
  1503. 02.06.2018 23:04:43, Alexandre Bourget - EOS Canada [@abourget]: wwwwwooott
  1504. 02.06.2018 23:05:02, Nathan Rempel | GenerEOS Sydney [@nsrempel]: awesome
  1505. 02.06.2018 23:05:29, Marc-Antoine Ross - EOS Canada [@marcantoineross]: w00t! that is great
  1506. 02.06.2018 23:06:19, Kevin Rose - EOS New York [@eosnewyork]: 👏 👏
  1507. 02.06.2018 23:07:20, Dafeng Guo - EOS Asia [@dftle]: that's awesome!
  1508. 02.06.2018 23:07:53, mini - EOS Argentina [@moonxor]: awesome!
  1509. 02.06.2018 23:08:09, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: [[Webpage]]I have not manually confirmed the cryptolion snapshot, but here is:
  1510.  
  1511. eosdac: https://github.com/eosdac/conversion/tree/master/eos%20final%20snapshot/v1
  1512.  
  1513. eosauthority: https://github.com/eosauthority/genesis/tree/master/snapshot-files/final/2
  1514. 02.06.2018 23:09:53, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: 👍👍
  1515. .....02.06.2018 23:13:29, - eoseoul.io DS Lim [@dslim]: >>invited Yongkil Kwon - EOSeoul.io<<
  1516. 02.06.2018 23:17:29, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Update on news, we are back to 2 confirmed snapshot, Bohdan and Rohan matched for period 350 but Bohdan’s server crashed for final snapshot!
  1517. 02.06.2018 23:17:47, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: [[Webpage]]These are matching snapshots so far:
  1518.  
  1519. eosdac: https://github.com/eosdac/conversion/tree/master/eos%20final%20snapshot/v1
  1520.  
  1521. eosauthority: https://github.com/eosauthority/genesis/tree/master/snapshot-files/final/2
  1522. 02.06.2018 23:21:27, mini - EOS Argentina [@moonxor]: [[Photo]]
  1523. 02.06.2018 23:21:28, mini - EOS Argentina [@moonxor]: @zhaoyu @dftle @marcantoineross @abourget if the information is valid(
  1524. peer fullnode.eoslaomao.com:443, the snapshot marc gave us, the block number, and the genesis)
  1525.  
  1526. there are some accouns that are not created, and some that dosent have the right stake
  1527. 02.06.2018 23:21:56, mini - EOS Argentina [@moonxor]: one of the accounts that dosent exist is g43tanryhege
  1528. 02.06.2018 23:22:22, mini - EOS Argentina [@moonxor]: we check that by hand, we are looking the wrong stakes to see if its an error on our side
  1529. 02.06.2018 23:22:37, Marc-Antoine Ross - EOS Canada [@marcantoineross]: The chain has not been updated yet, it's still the run from this afternoon which has been forked on ABP handoff
  1530. 02.06.2018 23:22:53, Alexandre Bourget - EOS Canada [@abourget]: Do you want to peer with a new chain ?
  1531. 02.06.2018 23:23:08, Alexandre Bourget - EOS Canada [@abourget]: I have a new genesis.json and have loaded the final/2 snapshot from EOS Authority..
  1532. 02.06.2018 23:24:27, mini - EOS Argentina [@moonxor]: well, if the block that you guys gave me was before the fork, it dosent matter. the accounts should be created before eosio resigns.
  1533. 02.06.2018 23:24:29, mini - EOS Argentina [@moonxor]: sure
  1534. 02.06.2018 23:24:52, Alexandre Bourget - EOS Canada [@abourget]: genesis.json: {"initial_timestamp":"2018-06-03T02:47:08","initial_key":"EOS6P3bsRaNLLLmmqTCf8XwCRPSbPUFivkcDsjkh36WR8KGjqTrLh"}
  1535. 02.06.2018 23:25:04, Alexandre Bourget - EOS Canada [@abourget]: give me a peer address, I'll sync you the blocks and you can quadruple-check :)
  1536. 02.06.2018 23:26:26, Marc-Antoine Ross - EOS Canada [@marcantoineross]: The node was not synced so the fork happened before the resignation block
  1537. 02.06.2018 23:27:24, mini - EOS Argentina [@moonxor]: [[Webpage]]I need a
  1538. - p2p endpoint
  1539. - block number after eosio resigns
  1540.  
  1541.  
  1542. We are going to use
  1543. genesis:
  1544. {"initial_timestamp":"2018-06-03T02:47:08","initial_key":"EOS6P3bsRaNLLLmmqTCf8XwCRPSbPUFivkcDsjkh36WR8KGjqTrLh"}
  1545.  
  1546. snapshot:
  1547. https://github.com/eosauthority/genesis/tree/master/snapshot-files/final/2
  1548. 02.06.2018 23:27:56, mini - EOS Argentina [@moonxor]: that make sense :D.
  1549. 02.06.2018 23:29:48, mini - EOS Argentina [@moonxor]: there is the problem with the stakes also.
  1550. 02.06.2018 23:30:22, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: were you validating against period 350 or latest
  1551. 02.06.2018 23:30:45, mini - EOS Argentina [@moonxor]: to this block @syed_jafri
  1552. 02.06.2018 23:31:03, Marc-Antoine Ross - EOS Canada [@marcantoineross]: do you have details ?
  1553. 02.06.2018 23:31:21, mini - EOS Argentina [@moonxor]: yes, 1 sec
  1554. 02.06.2018 23:35:20, mini - EOS Argentina [@moonxor]: [[Photo]]
  1555. 02.06.2018 23:35:53, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: rounding errors
  1556. 02.06.2018 23:37:52, Alexandre Bourget - EOS Canada [@abourget]: interesting :P
  1557. 02.06.2018 23:38:11, mini - EOS Argentina [@moonxor]: [[Document, size 34'700 bytes]]
  1558. 02.06.2018 23:38:12, Alexandre Bourget - EOS Canada [@abourget]: what am I seeing.. so L is what is in the account, C is CPU and N is Net ?
  1559. 02.06.2018 23:38:28, mini - EOS Argentina [@moonxor]: exactly
  1560. 02.06.2018 23:38:39, mini - EOS Argentina [@moonxor]: most likley the csv was wrong
  1561. 02.06.2018 23:38:54, Alexandre Bourget - EOS Canada [@abourget]: ok, is it possible that the split algo does the rounding resolution on the other way
  1562. 02.06.2018 23:39:33, Alexandre Bourget - EOS Canada [@abourget]: [[Webpage]]no no.. look: https://github.com/eoscanada/eos-bios/blob/master/bios/ops.go#L417-L419
  1563. 02.06.2018 23:39:47, Alexandre Bourget - EOS Canada [@abourget]: if there is rounding on the first, the other will get the off-by-one..
  1564. 02.06.2018 23:40:21, Alexandre Bourget - EOS Canada [@abourget]: if your validation tool uses a slightly different algo, it might be off-by-one..
  1565. 02.06.2018 23:40:31, Alexandre Bourget - EOS Canada [@abourget]: so maybe we can tolerate a difference of 0.0001 EOS, what do you think ?
  1566. 02.06.2018 23:41:47, mini - EOS Argentina [@moonxor]: most likely we are looking to a chain that wasnt boot with the same snapshot
  1567. 02.06.2018 23:42:16, mini - EOS Argentina [@moonxor]: 162 != 164
  1568. 02.06.2018 23:42:34, mini - EOS Argentina [@moonxor]: I would think that there shouldnt be no tolerance
  1569. 02.06.2018 23:43:09, Alexandre Bourget - EOS Canada [@abourget]: well we need the same rounding algorithm
  1570. 02.06.2018 23:43:18, Alexandre Bourget - EOS Canada [@abourget]: can you report the two unequal values ?
  1571. 02.06.2018 23:44:35, WinLin-EOSBIXIN [@hiwinlin]: I think we need to use the Decimal type to calculate and compare
  1572. 02.06.2018 23:45:03, Nathan Rempel | GenerEOS Sydney [@nsrempel]: setup the new genesis, waiting for blocks to start coming in
  1573. 02.06.2018 23:45:05, Nathan Rempel | GenerEOS Sydney [@nsrempel]: chain id 67fc1919ce5f203b0ba1f315ad9059a04056b17b9ac056ccba7a5c8ebd98554a
  1574. 02.06.2018 23:48:22, mini - EOS Argentina [@moonxor]: >>>(100000.0 + 772116.0 + 772116.0)/10000.0
  1575. 164.4232
  1576.  
  1577. vs 162.4232 in the chain
  1578. 02.06.2018 23:49:33, Nathan Rempel | GenerEOS Sydney [@nsrempel]: no getting anything synced... if someone wants to peer with p2p.genereos.io:9876 would be sweet
  1579. 02.06.2018 23:54:19, mini - EOS Argentina [@moonxor]: we need a synced peer :(
  1580. 02.06.2018 23:55:08, Alexandre Bourget - EOS Canada [@abourget]: let's put peering into in BIOS Boot..
  1581. 02.06.2018 23:55:08, Alexandre Bourget - EOS Canada [@abourget]: I'm about to diffuse a new genesis.json ..
  1582. 03.06.2018 00:02:14, mini - EOS Argentina [@moonxor]: instead of leaving the initial configuration empty, you can run
  1583. nodeos —print-genesis , to generate a valid genesis.
  1584. 03.06.2018 00:03:47, mini - EOS Argentina [@moonxor]: the validator shows the first error, in the stage 20 case, the first error was the timestamp, but the initial params were also wrong, because they were empty.
  1585. 03.06.2018 00:17:43, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: agreed
  1586. 03.06.2018 00:18:04, Alexandre Bourget - EOS Canada [@abourget]: it just means using the defaults.. should we have validation errors because of that ?
  1587. 03.06.2018 00:18:43, Alexandre Bourget - EOS Canada [@abourget]: which validation errors were triggered on the timestamp ?
  1588. 03.06.2018 00:19:07, mini - EOS Argentina [@moonxor]: the genesis used to launch is not the same as the one in the chain, we are validating that
  1589. 03.06.2018 00:19:27, mini - EOS Argentina [@moonxor]: [[Webpage]]https://docs.google.com/document/d/1Bsi1__u7U4Jvl9JAomdtWu7U0DaWGPcmD9FIAzL_pQM/edit#heading=h.qtvfems4zceg
  1590. .....03.06.2018 00:24:52, - eoseoul.io DS Lim [@dslim]: >>invited Sangwook Lee_EOSeoul.io [@NEOPLY]<<
  1591. 03.06.2018 00:53:03, Alexandre Bourget - EOS Canada [@abourget]: you only need to check the chain_id.. it's a hash of timestamp + initialpubkey
  1592. 03.06.2018 00:53:27, Alexandre Bourget - EOS Canada [@abourget]: you want to check parameters too ? eos-bios doesn't write parameters.. it relies on the default params of the boot node
  1593. 03.06.2018 00:54:46, Alexandre Bourget - EOS Canada [@abourget]: is that still an issue ? this doesn't seem like a rounding error, does it ?
  1594. 03.06.2018 00:59:47, mini - EOS Argentina [@moonxor]: I need the p2p endpoint and the block number to validate, if you could give me one would be awesome. I'm going home right now to get some sleep :( , but i can do it in a couple of hours
  1595. 03.06.2018 01:00:11, Alexandre Bourget - EOS Canada [@abourget]: ok, get some rest.. it's important.. I'll have an endpoint and block height to validate..
  1596. 03.06.2018 01:00:28, Alexandre Bourget - EOS Canada [@abourget]: the chain is currently frozen, in the sense that no tx can get in (locked by contract-whitelist)
  1597. 03.06.2018 01:00:56, mini - EOS Argentina [@moonxor]: :) i'm in a car right now otherwise would be happy to do it now
  1598. .....03.06.2018 01:08:45, Hahn - EOS NodeOne [@hahnryu]: >>invited Leo Seo - EOS NodeOne [@sspleo]<<
  1599. 03.06.2018 02:10:31, Rohan - EOSauthority [@RohanWillAnswer]: Hello, Good morning.. I’m back up.. Did anyone else get the final snapshots?
  1600. 03.06.2018 02:10:48, Rohan - EOSauthority [@RohanWillAnswer]: Trying to catch up with all the other messages
  1601. .....03.06.2018 02:40:38, Tim Weston - GenerEOS (BP Sydney) [@timweston]: >>invited Tom Fu GenerEOS (BP Sydney) [@Fuble]<<
  1602. 03.06.2018 03:05:42, Rohan - EOSauthority [@RohanWillAnswer]: Ok, I have some good news..
  1603. 03.06.2018 03:06:04, Rohan - EOSauthority [@RohanWillAnswer]: [[Webpage]]This is kinda amazing!! I can’t believe it..
  1604. EOS Authority - Folder 2 (our last version) is a perfect match with EOS DAC i compared this morning!
  1605.  
  1606. Do a diff on snapshot.csv and snapshot_unregistered.csv
  1607.  
  1608. Links:
  1609. https://github.com/eosauthority/genesis/tree/master/snapshot-files/final/2 (EOS Authority - Final 2 - 6 hours ago)
  1610. https://github.com/eosdac/conversion/tree/master/eos%20final%20snapshot/v1 (EOS Dac v1 - 4 hours ago)
  1611.  
  1612. Will wait for other BPs snapshots as well.
  1613.  
  1614. @syed_jafri @sandw1ch @Lifex10 @igorls @abourget @BohdanCryptoLions
  1615. 03.06.2018 03:07:04, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Awesome !!!
  1616. 03.06.2018 03:08:02, Hahn - EOS NodeOne [@hahnryu]: Great! Much earlier than I thought!
  1617. 03.06.2018 03:08:09, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: That’s Fantastic!!!
  1618. 03.06.2018 03:09:51, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: [[GIF, size 132'456 bytes]]
  1619. 03.06.2018 03:10:31, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: We still want atleast 3 independant confirmations, ideally 5
  1620. 03.06.2018 03:10:40, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I believe @deckw’s node kept failing too
  1621. 03.06.2018 03:11:47, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: Agreed. But this is a great start.
  1622. 03.06.2018 03:12:28, Rohan - EOSauthority [@RohanWillAnswer]: I had two nodes running. One crashed and had to be restarted..
  1623. 03.06.2018 03:12:36, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Yes, we’ve known EOS Authority and eosDAC have been matching for over 4 hours
  1624. 03.06.2018 03:12:56, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: He said
  1625. 03.06.2018 03:12:59, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: he restarted twice
  1626. 03.06.2018 03:13:03, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: doing it 3rd time..
  1627. 03.06.2018 03:56:23, Sam - EOS Dublin [@samnoble]: That's not cool. What are you crashing on?
  1628. 03.06.2018 03:57:06, Rohan - EOSauthority [@RohanWillAnswer]: That was yesterday.. A restart worked fine..
  1629. 03.06.2018 03:57:18, Sam - EOS Dublin [@samnoble]: Awesome
  1630. .....03.06.2018 03:58:50, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>changed group name to "EOS Validation (EMLG)"<<
  1631. 03.06.2018 04:01:19, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Can we agree to use this channel for EOS MAINNET LAUNCH validation communications.
  1632.  
  1633. I believe all key people are here
  1634.  
  1635. Please note we cannot launch until we have Governance Documents , looks like they will be a couple of hours.
  1636.  
  1637. Cool heads guys.
  1638.  
  1639. Let’s do this!!
  1640. 03.06.2018 04:02:23, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: We had @maoyifeng, @DenisCarriere and @dftle work hard today in including the Ricardian contracts
  1641. 03.06.2018 04:02:37, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: We also included the Consitution into the abi
  1642. 03.06.2018 04:04:55, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I see @dftle in the other discussions , it’s coming together!
  1643. 03.06.2018 04:10:29, Igor Lins e Silva - EOS Rio [@igorls]: {{FWD: Igor Lins e Silva - EOS Rio [@igorls], 03.06.2018 04:10:17}}
  1644. [[Document, size 19'949'615 bytes]]
  1645. .....03.06.2018 04:13:55, Lachezar Iordanov [@LachezarIordanov]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1646. .....03.06.2018 04:14:00, Alex - EOS SOCAL [@gmory]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1647. .....03.06.2018 04:14:24, Lachezar Iordanov [@LachezarIordanov]: >>invited J.T. - EOS the World [@HartParr]<<
  1648. .....03.06.2018 04:14:25, Libai - Eosio.SG [@Libai_EosioSG]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1649. .....03.06.2018 04:15:08, Guillaume @eostitan.com [@gyom_eos_titan]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1650. .....03.06.2018 04:15:17, Ben Sigman [@Bensig]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1651. .....03.06.2018 04:15:42, Leon - EOSIO.SG [@leonsun]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1652. .....03.06.2018 04:16:17, Andrey Marchuk [@madz7z]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1653. .....03.06.2018 04:16:31, [email protected] [@qianxiaofeng]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1654. .....03.06.2018 04:16:54, Jack - AcroEOS [@gjacklee]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1655. .....03.06.2018 04:17:31, Jack - AcroEOS [@gjacklee]: >>unsupported service message type: messageActionChatAddUsers<<
  1656. 03.06.2018 04:17:38, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Welcome everyone, let’s keep this focused on Validation and Mainnet Prep.
  1657.  
  1658. Eric and I are the only admins.
  1659.  
  1660. Any shit or unwanted peeps let me know.
  1661. 03.06.2018 04:27:08, Rohan - EOSauthority [@RohanWillAnswer]: Sounds good..
  1662. 03.06.2018 04:27:27, Rohan - EOSauthority [@RohanWillAnswer]: [[Webpage]]We’ve also loaded our latest snapshot on https://eosauthority.com
  1663. 03.06.2018 04:27:32, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: [[Webpage]]VALIDATION REPORT:
  1664.  
  1665. I have personally validated the output files from EOS Authority, EOS Rio and eosDAC and they all have the same output files and output checksums!
  1666.  
  1667. Here is an ongoing repository with all snapshots: https://github.com/eoscafe/eos-snapshot-validation
  1668. 03.06.2018 04:27:44, Rohan - EOSauthority [@RohanWillAnswer]: No reports of any issues on balances..
  1669. 03.06.2018 04:30:07, Rohan - EOSauthority [@RohanWillAnswer]: Excellent news! 👍
  1670. 03.06.2018 04:30:29, Rohan - EOSauthority [@RohanWillAnswer]: Awesome!!
  1671. 03.06.2018 04:31:01, Ralf Weinand | GenerEOS (BP Sydney) [@RalfWei]: Excellent work guys! 3 independent matching validations. We are getting close...
  1672. 03.06.2018 04:33:13, Roshan - EOS Authority [@telepound]: excellent.
  1673. 03.06.2018 05:07:14, Hahn - EOS NodeOne [@hahnryu]: I just shared the news to the community that EOSAuthority&eosDAC snapshots were found identical. And there was a person who claimed that there's difference in what is seen between MEW contract key string/EOSCountdown and EOS Authority&eosDAC snapshot. He said he registered the same eth wallet twice to make sure it is properly registered, once in last feb, and once in 28th May. While MEW Contract Key String & eoscountdown.com shows his newly resigered public key, The eosdac/eosauthority snapshot seems to show his old one.
  1674.  
  1675. His ETH Address : 0xF828CCEc5c3744D0F56a67cfab736066fc3Bd6A6
  1676.  
  1677. [Mew Contract Key String / eoscountdown.com] :
  1678. EOS8QunSrNAfdtyx2MT5gnYkisJVNYFwUJ8ttMDKVuCTLgfkxEko3
  1679.  
  1680. [eosauthority / eos dac Snapshot] :
  1681. EOS66VYof6zt8yRXQYjw7zKMWQgWZpoBgXHUU5cp8iTUCFVa4uAUP
  1682.  
  1683. He's now confused which is right one.
  1684. Guess there might be more of these cases where people registered the same ETH address for more than twice.
  1685. 03.06.2018 05:17:15, David P - EOS42 [@GunnisonCap]: Logically the registration did not work on the second attempt properly due to lack of gas etc. Otherwise it would have overwritten the previous.
  1686. 03.06.2018 05:18:40, Hahn - EOS NodeOne [@hahnryu]: He thought it's overwritten successfuly when he checked from eoscountdown.com, but what happen to appear in the snapshot is still the old one.
  1687. 03.06.2018 05:18:49, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: He has 5000 EOS
  1688. 03.06.2018 05:18:51, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: registered
  1689. 03.06.2018 05:19:05, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: with ETH key 0xF828CCEc5c3744D0F56a67cfab736066fc3Bd6A6
  1690. 03.06.2018 05:19:09, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: tell him to vote for me 😉
  1691. 03.06.2018 05:22:14, Dafeng Guo - EOS Asia [@dftle]: great news
  1692. .....03.06.2018 06:40:38, Dan Levine [@dannymaximo]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1693. .....03.06.2018 06:41:49, CRS [@sss_CRS_sss]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1694. .....03.06.2018 06:52:12, Eric_EOSARMY.io [@Eric_EOSARMY]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1695. 03.06.2018 07:29:07, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]https://zoom.us/j/581561479
  1696. 03.06.2018 07:29:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Opening a Zoom Room for Validation
  1697. 03.06.2018 07:35:07, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: [[Webpage]]🚀 VALIDATION UPDATE 🚀
  1698.  
  1699. I have verified snapshots from the following 5 BPs + 1 Independant to match:
  1700. 1. EOS Authority
  1701. 2. EOS Rio
  1702. 3. eosDAC
  1703. 4. EOSphere
  1704. 5. EOS New York
  1705. 6. Max Infeld
  1706.  
  1707. The snapshot from EOS Store had 2 discrepancies (they were only team using another tool than genesis, they used EOSBIXIN/eostoolkit). The discrepancies were in the accounts:
  1708. 1. 0x94a717c2a6f8e1b2b217fe9b49d04b8de0e430ce
  1709. 2. 0x69d645ad13ca271ddee97da896dae0822516ecfe
  1710.  
  1711. EOS Asia is currently running a snapshot, message me with any other snapshots you find.
  1712.  
  1713. The updated repo with all snapshots is here: https://github.com/eoscafe/eos-snapshot-validation
  1714. .....03.06.2018 07:36:11, Ken (EOSphere) [@ken_eosphere]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1715. 03.06.2018 07:36:12, Roman CryptoLions [@romanskaskiw]: 👍
  1716. 03.06.2018 07:43:26, David P - EOS42 [@GunnisonCap]: Excellent work Syed
  1717. 03.06.2018 07:44:28, Leonard Dorlöchter - EOS network by Advanced Blockchain AG [@EOSnetwork]: 👍
  1718. .....03.06.2018 08:02:28, Jose Toriello [@josetoriello]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1719. .....03.06.2018 08:03:07, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1720. 03.06.2018 08:03:36, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: there are two accounts missing in EosStore snapshot
  1721. 03.06.2018 08:04:46, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I would suggest if we have 5 matching snapshots we are good. And others need to validate against that base if they still see the need.
  1722. 03.06.2018 08:06:23, deck - EOS New York [@deckw]: Agreed. I believe the next step is to come to an agreement on the final code to use correct?
  1723. .....03.06.2018 08:06:36, Luis Fernando G : EOSMESOdotio 🇬🇹 [@Maski_LF]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1724. 03.06.2018 08:06:47, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Yes @jemxpat what's the current situation on this?
  1725. 03.06.2018 08:07:06, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: we checked these two accounts with both the etherscan.io and etherchain.org, pretty sure EosScore snapshot missed them out
  1726. 03.06.2018 08:07:20, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Cool
  1727. .....03.06.2018 08:07:40, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>unsupported service message type: messageActionPinMessage<<
  1728. 03.06.2018 08:07:47, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: with balance ~12 EOS and 10 EOS each
  1729. 03.06.2018 08:08:36, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I've pinned @syed_jafri last update so teams can check against that.
  1730.  
  1731. I will continue to pin the most recent validation update as we go through today.
  1732. 03.06.2018 08:09:19, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Have a zoom room ready if we need it. Don't see any need at the moment.
  1733. 03.06.2018 08:11:04, Dafeng Guo - EOS Asia [@dftle]: I like how Syed did it for snapshot validation which we try to set specific goals that once reached we are confident to move to next stage.
  1734. 03.06.2018 08:29:27, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Agreed , awesome job
  1735. 03.06.2018 08:39:29, Devin Lee KOREOS.IO [@indend007]: How about these accounts with "0" balance? Is this removed snapshot? Even if is already registered?
  1736. 03.06.2018 08:42:46, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Hi everyone! How are we doing on validation of the last run? Can I help centralize all issues found somewhere?
  1737. 03.06.2018 08:45:52, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]Can teams join us here https://zoom.us/j/581561479
  1738. 03.06.2018 08:46:07, Sharif Bouktila - EOS Dublin [@sharifbouktila]: to discuss next steps
  1739. 03.06.2018 08:57:01, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]https://docs.google.com/document/d/1Bsi1__u7U4Jvl9JAomdtWu7U0DaWGPcmD9FIAzL_pQM/edit#heading=h.qtvfems4zceg
  1740. .....03.06.2018 08:57:07, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>unsupported service message type: messageActionPinMessage<<
  1741. 03.06.2018 08:58:17, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I've pinned his document. We need to agree what tests are needed for Successful Validation
  1742. .....03.06.2018 09:10:19, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>invited Josh Kauffman - EOS Canada [@joshkauff]<<
  1743. 03.06.2018 09:19:28, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]We will then take the information from the Pinned Document and work into this Test Plan
  1744.  
  1745. https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit?usp=sharing
  1746. 03.06.2018 09:19:49, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Please fire ahead if you can. It should be very clear and simple to follow
  1747. 03.06.2018 09:28:26, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Document, size 188'738 bytes]]
  1748. 03.06.2018 09:28:26, Sharif Bouktila - EOS Dublin [@sharifbouktila]: As a starting point I've included the tests as listed in this Flow Diagram.
  1749. 03.06.2018 09:59:34, Josh Kauffman - EOS Canada [@joshkauff]: Hey all. Just wanted to pass along the info that all changes that were needed for Governance documents, as well as updating the ABIs have all been done and merged. All good to go.
  1750. 03.06.2018 10:00:29, Jose Toriello [@josetoriello]: I can confirm this.
  1751. 03.06.2018 10:00:33, Nathan Rempel | GenerEOS Sydney [@nsrempel]: woo
  1752. 03.06.2018 10:00:59, Jose Toriello [@josetoriello]: Meaning it is confirmed. Done
  1753. 03.06.2018 10:01:26, mao EOSREAL [@maoyifeng]: GREAT!
  1754. 03.06.2018 10:03:26, Daniel Larimer [@daniellarimer]: 😎
  1755. 03.06.2018 10:03:53, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Great work team! Let's make sure this is in the validation spreadsheet
  1756. 03.06.2018 10:05:51, Rick Schlesinger - EOS New York [@unlockrs]: 👍
  1757. 03.06.2018 10:06:55, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Can I suggest a cut-off of 14:30 UTC for suggesting tests (24 mins from now)
  1758. 03.06.2018 10:07:52, Tim Weston - GenerEOS (BP Sydney) [@timweston]: 👍🏻
  1759. 03.06.2018 10:08:39, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: Awesome!
  1760. 03.06.2018 10:32:54, Alexandre Bourget - EOS Canada [@abourget]: @xebb82 I didn't yet do the block split of resignation actions.. do you think I should ?
  1761. 03.06.2018 10:33:30, Alexandre Bourget - EOS Canada [@abourget]: I'll push this chain out for people to test.. and I'll try to fit it in.. so the next run could be forkable like you wanted.
  1762. 03.06.2018 10:39:17, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Document, size 437'889 bytes]]
  1763. 03.06.2018 10:40:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: This is what we have in the spreadsheet now.
  1764.  
  1765. If we can all move and work there. And make sure we have tests listed and the approach to test each one.
  1766.  
  1767. We will review them on the Zoom call in 1 hour from now 15:40
  1768.  
  1769. Agreed ???????
  1770. .....03.06.2018 10:47:06, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>unsupported service message type: messageActionPinMessage<<
  1771. 03.06.2018 10:47:20, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Test Plan is now pinned
  1772. 03.06.2018 11:10:35, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We have 28 people in our Zoom Call
  1773.  
  1774. We will be reviewing the Test Plan to try reach consensus at 15:45 UTC - 35 Minutes from now.
  1775. .....03.06.2018 11:15:55, Joe EOS Asia [@gaijinJOE]: >>invited 彭 皓 [@hericpeng]<<
  1776. 03.06.2018 11:47:27, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]If you aren't already in can you join our Zoom Call
  1777.  
  1778. https://zoom.us/j/581561479
  1779. 03.06.2018 11:47:40, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We can start to look at the Test Plan in 5 minutes
  1780. 03.06.2018 11:48:12, mini - EOS Argentina [@moonxor]: +1
  1781. 03.06.2018 12:59:38, David P - EOS42 [@GunnisonCap]: Can’t make it unfortunately but about to review the plan and will add comments @sharifbouktila
  1782. 03.06.2018 13:18:46, David P - EOS42 [@GunnisonCap]: Few changes made, one I added in relates to whether we want to carry out a coordinated transaction as part of the pause/restart of the chain to simulate implementation of an arbitration ruling.
  1783. 03.06.2018 13:19:07, David P - EOS42 [@GunnisonCap]: Arguably that's one we can do on a testnet and doesn't need to be for the mainnet validation actually
  1784. 03.06.2018 13:19:27, David P - EOS42 [@GunnisonCap]: I'll scrap it, but we do need to practice for such scenarios post launch
  1785. 03.06.2018 14:32:20, Sam - EOS Dublin [@samnoble]: [[Webpage]]All, thanks again for the meeting just now, I think we made some awesome progress! A quick summary of the plan between now and the next meeting which will take place at 1300 UTC on Monday 4th June 2018.
  1786.  
  1787. - Firestarter will be used to perform chain validation with the following testers:
  1788. - Buddy @ EOS New York
  1789. - Trenton @ CSX.IO
  1790. - Mini @ EOS Argentina
  1791.  
  1792. - Everyone else will use the master spreadsheet to perform testing on the net that EOS Canada (EOSIO BIOS BOOT) have running to test as many of the test cases as possible. Sheet is here: https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=0
  1793.  
  1794. Please remember to document what you do and your results as we can use this for auditing later.
  1795.  
  1796. During the call tomorrow, we'll aim to:
  1797.  
  1798. - Compare notes on our testing
  1799. - Detail any concerns/issues/bugs and how to address them
  1800. - Agree on the next steps
  1801.  
  1802. We're getting very close to getting EOS in to the hands of the community, we just have to continue working together towards this common goal and take it step by step. Remember, it's a marathon and not a race!
  1803.  
  1804. See you all tomorrow at 1300 UTC!
  1805. 03.06.2018 14:38:36, Jose Toriello [@josetoriello]: 👍 Thanks for the leadership
  1806. 03.06.2018 14:38:58, Jose Toriello [@josetoriello]: And also @moonxor even though he is reluctant
  1807. 03.06.2018 14:39:11, Jose Toriello [@josetoriello]: 😜
  1808. 03.06.2018 14:55:47, Denis | EOS Nation [@DenisCarriere]: ⭐️Bang on!
  1809. 03.06.2018 14:57:16, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Great work everyone! Let's leave no stone unturned!
  1810. 03.06.2018 15:21:46, mini - EOS Argentina [@moonxor]: lol, I can help to coordinate the validation if you guys want to, no problem
  1811. 03.06.2018 15:21:50, mini - EOS Argentina [@moonxor]: +1
  1812. 03.06.2018 15:23:04, deck - EOS New York [@deckw]: taking a look now.
  1813. 03.06.2018 15:25:24, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: We need atleast 5 testers
  1814. 03.06.2018 15:25:42, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: With 3 testers, if 1 person is a little off, you’re not sure if the chain is screwed or they screwed up
  1815. 03.06.2018 15:26:16, Rick Schlesinger - EOS New York [@unlockrs]: Agreed. Need more testers please.
  1816. 03.06.2018 15:26:45, mini - EOS Argentina [@moonxor]: we can make a call in about 3/4 hours
  1817. 03.06.2018 15:26:59, mini - EOS Argentina [@moonxor]: so I can show you how to run firestarter
  1818. 03.06.2018 15:27:05, mini - EOS Argentina [@moonxor]: maybe i can work in more documentation
  1819. 03.06.2018 15:27:16, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: A chain is not validated in my opinion without 5 independant testers atleast
  1820. 03.06.2018 15:27:24, mini - EOS Argentina [@moonxor]: +1
  1821. 03.06.2018 15:27:30, mini - EOS Argentina [@moonxor]: I think every abp should validate the chain
  1822. 03.06.2018 15:27:33, mini - EOS Argentina [@moonxor]: but thats my opinion
  1823. 03.06.2018 15:27:36, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: agreed
  1824. 03.06.2018 15:27:50, Rick Schlesinger - EOS New York [@unlockrs]: +1
  1825. 03.06.2018 15:29:47, deck - EOS New York [@deckw]: he said signing himself up :)
  1826. 03.06.2018 15:30:21, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I could, but I would rather stay independant coordinating the tests
  1827. 03.06.2018 15:30:44, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I believe doing the testing sort of adds bias to which other validations you confirm
  1828. 03.06.2018 15:34:33, deck - EOS New York [@deckw]: I was just teasing. What you have been doing adds a ton of value for sure. Might be worthwhile to have you takeover @moonxor's job of Test Manager
  1829. 03.06.2018 15:35:37, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Yes we need @moonxor to focus on teaching people how to use the tool
  1830. 03.06.2018 15:36:10, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: The tool README doesnt look too complicated we could have a dozen or so BPs run through it
  1831. 03.06.2018 15:40:37, deck - EOS New York [@deckw]: not at all complicated. Running now
  1832. 03.06.2018 15:45:13, mini - EOS Argentina [@moonxor]: ❤️
  1833. 03.06.2018 15:48:21, mini - EOS Argentina [@moonxor]: I think the tool is quite simple and dosent need a lot of teaching. Also my english skills are not top notch
  1834. 03.06.2018 15:52:17, mini - EOS Argentina [@moonxor]: I wouldnt be comfortable with anyone been a manager right now, I think we need p2p consensus not a manager. I like what @dftle said about dividing ourselves in tasks.
  1835.  
  1836. we need:
  1837.  
  1838. 1- reach consensus on what a valid blockchain is (BOOT CONSENSUS)
  1839.  
  1840. 2- Before opening the main chain we need to test if the SOFTWARE is working fine. we need to reach a consensus on what means "software working fine".
  1841.  
  1842.  
  1843. after we reach consensus on 1 and 2 we then can think about who would test that and how.
  1844. 03.06.2018 15:54:56, Basit Raza - EOSVibes [@boltxyz]: [[Webpage]]https://github.com/EOSVibes/eos-validation-results
  1845. here is result of check contracts, check accounts, intitial EOS balance using eospy validation script
  1846. 03.06.2018 16:02:32, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Agreed not a manager , but appreciate the work to put some structure on the Test Approach and Plan
  1847. 03.06.2018 16:03:01, mini - EOS Argentina [@moonxor]: yes, i can do that %100.
  1848. 03.06.2018 16:04:12, deck - EOS New York [@deckw]: Hey someone used my tool!!
  1849. 03.06.2018 16:04:23, deck - EOS New York [@deckw]: Even better it worked haha
  1850. 03.06.2018 16:04:57, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I think manager is a bad term, what we all mean is coordinator
  1851. 03.06.2018 16:05:00, deck - EOS New York [@deckw]: Err I mean of course it would
  1852. 03.06.2018 16:05:27, mini - EOS Argentina [@moonxor]: i like temporary sudoer ❤️
  1853. 03.06.2018 16:05:35, mini - EOS Argentina [@moonxor]: anyone running the mainnet repo?
  1854. 03.06.2018 16:05:51, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: jungle is I believe
  1855. 03.06.2018 16:06:04, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: theyre not using the exact final snapshot though
  1856. 03.06.2018 16:06:09, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: theyre using eosauthority/v1
  1857. 03.06.2018 16:06:14, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: which is missing 2 accounts
  1858. 03.06.2018 16:06:20, mini - EOS Argentina [@moonxor]: i think we should start filling the ricardiang contracts fields in the eosiosystem.abi otherwise the chain would not have a constituttion
  1859. 03.06.2018 16:06:29, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: we have already been doing that
  1860. 03.06.2018 16:06:33, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: 🙂
  1861. 03.06.2018 16:06:36, mini - EOS Argentina [@moonxor]: awesome :D
  1862. 03.06.2018 16:07:09, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I found out they were missing 48 hours ago, and now @maoyifeng @dftle and @DenisCarriere have worked hard to put most of them in
  1863. 03.06.2018 16:07:30, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: We also put the constitution in eosio.system
  1864. 03.06.2018 16:07:45, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: [[Webpage]]https://github.com/EOS-Mainnet/eos/tree/launch-rc
  1865. .....03.06.2018 16:18:50, Lars Ihler - BitSpace [@LarsIhler]: >>invited Manuel Lains (spectral) [@spectralvision]<<
  1866. 03.06.2018 16:19:45, Alexandre Bourget - EOS Canada [@abourget]: Check the chain that is out there, "get code eosio -a dump.abi"
  1867. 03.06.2018 16:19:56, Alexandre Bourget - EOS Canada [@abourget]: Someone needs to cross check that too :-)
  1868. 03.06.2018 16:20:04, Alexandre Bourget - EOS Canada [@abourget]: Same for eosio.token
  1869. 03.06.2018 16:22:26, mini - EOS Argentina [@moonxor]: yes we are working on validating the chain with an endpoint that we took from eos-bios channel
  1870. 03.06.2018 16:22:41, mini - EOS Argentina [@moonxor]: and updating some stuff to firestarter
  1871. 03.06.2018 16:27:24, Alexandre Bourget - EOS Canada [@abourget]: Super cool :-) you bring a lot of value here mini :-)
  1872. 03.06.2018 16:28:08, mini - EOS Argentina [@moonxor]: would have love to finish firestarter a week or 2 ago :(. But thanks :D
  1873. 03.06.2018 18:15:04, Sharif Bouktila - EOS Dublin [@sharifbouktila]: https://reddit.app.link/UMoFK3PtsN
  1874.  
  1875. Anyone else see this yet?
  1876. 03.06.2018 18:17:09, mini - EOS Argentina [@moonxor]: yes, we are talking about that
  1877. 03.06.2018 18:18:41, Sandwich [@sandw1ch]: 🔥🔥🔥
  1878. 03.06.2018 18:19:14, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: He makes it sound so relaxing, like launching a main net is like a day at the spa!
  1879. 03.06.2018 18:24:57, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Its actually the way it should be conveyed to voters
  1880. 03.06.2018 18:25:33, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Its good to keep them calm for us to focus on launch
  1881. 03.06.2018 18:25:39, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: I agree, we are shareing that video. Thank you.
  1882. 03.06.2018 18:28:12, Jose Toriello [@josetoriello]: Great video
  1883. 03.06.2018 18:29:15, Marcin @eosgreen.io [@marcin_eosgreen]: ❤️ , he should make more videos like that, great presentation
  1884. 03.06.2018 19:16:15, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: A question.. when you buy ram (like when you create a new account with the param: --buy-ram-kbytes 8) that money/EOS spent... who gets them?
  1885. 03.06.2018 19:16:19, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: Are they burned?
  1886. 03.06.2018 19:16:40, Daniel Larimer [@daniellarimer]: Eosio.ram.
  1887. 03.06.2018 19:17:00, Daniel Larimer [@daniellarimer]: When you sell you get it back. Most of it
  1888. 03.06.2018 19:18:33, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: but, how can I sell the ram I used to create the new account? Would I need to destroy the account?
  1889. 03.06.2018 19:18:47, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: You cannot
  1890. 03.06.2018 19:18:49, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Its spent
  1891. 03.06.2018 19:19:05, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Unless they pay for it themselves
  1892. 03.06.2018 20:14:24, mini - EOS Argentina [@moonxor]: @abourget @marcantoineross we fix some stuff that were wrong in our side, and the validation looks fine, the only thing thats not working is the genesis, and we cant validate global params due to the problem with the genesis, but the rest is looking goooooood
  1893. 03.06.2018 20:14:57, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: is it still the decimal point problems in genesis?
  1894. 03.06.2018 20:15:10, mini - EOS Argentina [@moonxor]: is not just the problem with the decimal points
  1895. 03.06.2018 20:15:49, mini - EOS Argentina [@moonxor]: what I would recommend to eos-bios is to generate a genesis.json with nodeos and use that to boot
  1896. 03.06.2018 20:16:24, mini - EOS Argentina [@moonxor]: we are validating that the parameters that you use to boot the network are the same as the ones when eosio resigns.
  1897. 03.06.2018 20:16:54, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: ah, needs all params as well
  1898. 03.06.2018 20:16:59, mini - EOS Argentina [@moonxor]: yes
  1899. 03.06.2018 20:17:00, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: using nodeos sets them to empty
  1900. 03.06.2018 20:17:04, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: but eos-bios is missing it
  1901. 03.06.2018 20:17:08, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: yes, we should do that
  1902. .....03.06.2018 20:17:24, J.T. - EOS the World [@HartParr]: >>invited Brett Jeffery @ EOS the World [@EOStheWorld]<<
  1903. 03.06.2018 20:17:25, mini - EOS Argentina [@moonxor]: ïs a small detail but i think is important otherwise you can boot with x parameters and change them
  1904. 03.06.2018 20:18:41, Alexandre Bourget - EOS Canada [@abourget]: can you validate that we're simply using the default values ? I'd like to keep the genesis.json dissemination super easy
  1905. 03.06.2018 20:18:46, Alexandre Bourget - EOS Canada [@abourget]: like being able to tweet it :P
  1906. 03.06.2018 20:19:53, Alexandre Bourget - EOS Canada [@abourget]: so you'd be validating that no one fiddled with the defaults
  1907. 03.06.2018 20:20:25, mini - EOS Argentina [@moonxor]: that no one fiddled with the params you use at boot
  1908. 03.06.2018 20:20:41, mini - EOS Argentina [@moonxor]: the idea is to have a vainilla validator
  1909. 03.06.2018 20:20:45, mini - EOS Argentina [@moonxor]: so it can work with any tool :(
  1910. 03.06.2018 20:54:57, Ricardo Marlière - EOS Brazil [@rbmarliere]: using https://github.com/rbmarliere/validate_eos/blob/master/validate_eos.sh to validate balances here
  1911. .....03.06.2018 20:57:01, Jack - AcroEOS [@gjacklee]: >>invited 광영 정<<
  1912. 03.06.2018 20:59:12, Chitty 🅑 - EOS Argentina [@JChitty]: [[Webpage]]During this morning call, some of you were asking about how to quickly inject the snapshot into blockchain, we created this post that goes trough the techniques we used in FireStarter... this code is free to use and you can integrated into your tools https://steemit.com/eosio/@eosargentina/injecting-the-full-erc20-snapshot-in-under-6-minutes-firestarter
  1913. 03.06.2018 21:36:25, David P - EOS42 [@GunnisonCap]: Nice article guys, and great work on Firestarter
  1914. .....03.06.2018 22:07:02, Benjamin Wang | EOShenzhen [@iBenjaminWang]: >>unsupported service message type: messageActionChatJoinedByLink<<
  1915. .....03.06.2018 22:09:38, mao EOSREAL [@maoyifeng]: >>invited Sherman EOSREAL [@ShermanXie]<<
  1916. 03.06.2018 22:16:12, mini - EOS Argentina [@moonxor]: <3
  1917. 03.06.2018 22:20:04, Alexandre Bourget - EOS Canada [@abourget]: @moonxor ohh! now I understand why you want to check the params! because you tweak them on-chain !
  1918. 03.06.2018 22:20:39, Alexandre Bourget - EOS Canada [@abourget]: so you want to make sure they're back to their original values!
  1919. 03.06.2018 22:21:17, mini - EOS Argentina [@moonxor]: yes :) but anyone can do it not only for injection
  1920. 03.06.2018 22:21:40, Alexandre Bourget - EOS Canada [@abourget]: yes.. and it affects the whole network
  1921. 03.06.2018 22:21:46, mini - EOS Argentina [@moonxor]: exactly!
  1922. 03.06.2018 22:22:06, Alexandre Bourget - EOS Canada [@abourget]: and there's no issue syncing for nodes connecting ?
  1923. 03.06.2018 22:22:42, Alexandre Bourget - EOS Canada [@abourget]: they'll process as fast as possible and keep the huge transactions?
  1924. 03.06.2018 22:22:52, Alexandre Bourget - EOS Canada [@abourget]: but mini, can your validation re-check for the default values ?
  1925. 03.06.2018 22:23:07, Alexandre Bourget - EOS Canada [@abourget]: I'd prefer not distributing a big fat genesis.json...
  1926. 03.06.2018 22:23:36, mini - EOS Argentina [@moonxor]: we are already doing that
  1927. 03.06.2018 22:23:55, Alexandre Bourget - EOS Canada [@abourget]: if I have time, I'd like to try your injection strategy.. and you'll make sure all params are reset to defaults.. so we'll be safe
  1928. 03.06.2018 22:24:09, Alexandre Bourget - EOS Canada [@abourget]: very good.. thanks a lot :)
  1929. 03.06.2018 22:24:33, mini - EOS Argentina [@moonxor]: sure! no problem :)
  1930. 03.06.2018 22:24:48, mini - EOS Argentina [@moonxor]: if anyone has other chain to validate please let us know
  1931. 03.06.2018 22:25:04, Alexandre Bourget - EOS Canada [@abourget]: (let me know too :)
  1932. 03.06.2018 22:25:05, Alexandre Bourget - EOS Canada [@abourget]: g'night
  1933. 03.06.2018 22:25:13, mini - EOS Argentina [@moonxor]: haha sure
  1934. 03.06.2018 22:25:15, mini - EOS Argentina [@moonxor]: o/
  1935. 03.06.2018 22:25:58, Lucas @EOS Beijing [@LucasEosBeijing]: hello,eveyone
  1936. 03.06.2018 22:29:58, mini - EOS Argentina [@moonxor]: hi o/
  1937. 03.06.2018 22:42:52, Lucas @EOS Beijing [@LucasEosBeijing]: @abourget Hello, does the contract change?
  1938. 03.06.2018 22:43:21, Lucas @EOS Beijing [@LucasEosBeijing]: Where are you now?
  1939. 03.06.2018 23:58:49, Nathan Rempel | GenerEOS Sydney [@nsrempel]: ./validate_chain_at_block.sh 000017dee519f1785e571480fe72989ac2dc7e4d00ecd0aa925aba6e7af414e4
  1940. Waiting for snapshot to be taken ........ (please wait)
  1941. 03.06.2018 23:58:55, Nathan Rempel | GenerEOS Sydney [@nsrempel]: waiting and waiting 🤣
  1942. 03.06.2018 23:59:30, mini - EOS Argentina [@moonxor]: in the data folder
  1943. 03.06.2018 23:59:37, mini - EOS Argentina [@moonxor]: you can do tail -f name.log
  1944. 03.06.2018 23:59:49, mini - EOS Argentina [@moonxor]: we are working in a progress bar :( sorry guys
  1945. 03.06.2018 23:59:58, Nathan Rempel | GenerEOS Sydney [@nsrempel]: not complaining ;)
  1946. 04.06.2018 00:00:00, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i know its huge
  1947. 04.06.2018 00:00:04, mini - EOS Argentina [@moonxor]: im complaining 😆
  1948. 04.06.2018 00:00:07, Nathan Rempel | GenerEOS Sydney [@nsrempel]: hahaha
  1949. 04.06.2018 00:00:07, Lucas @EOS Beijing [@LucasEosBeijing]: waiting......
  1950. 04.06.2018 00:00:32, Lucas @EOS Beijing [@LucasEosBeijing]: It's better to go to bed.
  1951. 04.06.2018 00:00:48, Nathan Rempel | GenerEOS Sydney [@nsrempel]: difficult, its 2pm in sunny sydney
  1952. 04.06.2018 00:01:12, mini - EOS Argentina [@moonxor]: we try it with our boot that injects everything in under 100 blocks, so when we have to snapshot the block 6000 takes longer and you dont have any warning message
  1953. 04.06.2018 00:01:23, mini - EOS Argentina [@moonxor]: but its the replay
  1954. 04.06.2018 00:03:31, Nathan Rempel | GenerEOS Sydney [@nsrempel]: firestarter/validator/this/data ?
  1955. 04.06.2018 00:04:16, Sandwich [@sandw1ch]: 😍
  1956. 04.06.2018 00:07:23, Nathan Rempel | GenerEOS Sydney [@nsrempel]: can't find name.log
  1957. 04.06.2018 00:07:28, Nathan Rempel | GenerEOS Sydney [@nsrempel]: only eos.log
  1958. 04.06.2018 00:07:36, Gustavo Mick - EOS Argentina [@gustavomick]: pull again
  1959. 04.06.2018 00:07:51, Nathan Rempel | GenerEOS Sydney [@nsrempel]: kk
  1960. 04.06.2018 00:07:55, Gustavo Mick - EOS Argentina [@gustavomick]: 🙂
  1961. 04.06.2018 00:10:03, mini - EOS Argentina [@moonxor]: eos.log :) not name.log, didnt remember the name, si should have put <name>.log
  1962. 04.06.2018 00:10:25, mini - EOS Argentina [@moonxor]: tail -f eos.log
  1963. 04.06.2018 00:10:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I assume i need to update the genesis in "this" to match? or atleast the timestamp and start key
  1964. 04.06.2018 00:11:37, Gustavo Mick - EOS Argentina [@gustavomick]: just to confirm, are you trying to validate, or are you trying to validate an specific chain
  1965. 04.06.2018 00:11:57, Nathan Rempel | GenerEOS Sydney [@nsrempel]: trying to validate against the latest bios boot chain
  1966. 04.06.2018 00:12:02, Nathan Rempel | GenerEOS Sydney [@nsrempel]: that im synced to
  1967. 04.06.2018 00:13:25, Gustavo Mick - EOS Argentina [@gustavomick]: yes you need to updated that file or you can use parameters
  1968. 04.06.2018 00:15:00, Nathan Rempel | GenerEOS Sydney [@nsrempel]: ok i can see its starting to sync blocks now
  1969. 04.06.2018 00:15:18, Gustavo Mick - EOS Argentina [@gustavomick]: nice
  1970. 04.06.2018 00:15:56, Gustavo Mick - EOS Argentina [@gustavomick]: sorry if there is any glitch on those params, please push a pr if you think there is something to help with
  1971. 04.06.2018 00:16:07, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 👍
  1972. 04.06.2018 00:16:18, Nathan Rempel | GenerEOS Sydney [@nsrempel]: see how it works out once fully synced
  1973. 04.06.2018 00:18:23, Gustavo Mick - EOS Argentina [@gustavomick]: ok, depending on your hw, snapshot validation could take between 5-15 min. let us know if you have any issue.
  1974. 04.06.2018 00:22:39, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Waiting for snapshot to be taken ........ (please wait)
  1975. 1329899ms thread-0 snapshot_plugin.cpp:89 operator() ] Taking snapshot at block 6110 (000017dee519f1785e571480fe72989ac2dc7e4d00ecd0aa925aba6e7af414e4)...
  1976. Snapshot saved in /home/nathan/firestarter/validator/this/files/snapshot.bin
  1977. Converting snapshot to json ...
  1978. 04.06.2018 00:22:41, Nathan Rempel | GenerEOS Sydney [@nsrempel]: going well so far
  1979. 04.06.2018 00:24:11, Nathan Rempel | GenerEOS Sydney [@nsrempel]: got an error
  1980. 04.06.2018 00:24:12, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Converting snapshot to json ...
  1981. 1362909ms thread-0 snap2json.cpp:182 main ] 8 out_of_range_exception: Out of Range
  1982. read datastream of length 0 over by 1
  1983. {"method":"read","len":0,"over":1}
  1984. thread-0 datastream.cpp:6 throw_datastream_range_error
  1985. error unpacking uint64_t
  1986. {"type":"uint64_t"}
  1987. thread-0 raw.hpp:616 unpack
  1988. 1362909ms thread-0 snap2json.cpp:182 main ] :
  1989. Validating EOS blockchain snapshot against "EOS Vanilla validator (v0.1)"
  1990. Loading EOS snapshot FAIL
  1991.  
  1992. ##########################################################
  1993. No JSON object could be decoded
  1994. Traceback (most recent call last):
  1995. File "validator.py", line 27, in <module>
  1996. getattr(validator,'validate')(args)
  1997. File "/home/nathan/firestarter/validator/vanilla_validator.py", line 316, in validate
  1998. eos_snapshot = load_eos_snapshot(args)
  1999. File "/home/nathan/firestarter/validator/vanilla_validator.py", line 70, in load_eos_snapshot
  2000. snapshot = json.load(file)
  2001. File "/usr/lib/python2.7/json/__init__.py", line 291, in load
  2002. **kw)
  2003. File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
  2004. return _default_decoder.decode(s)
  2005. File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
  2006. obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  2007. File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
  2008. raise ValueError("No JSON object could be decoded")
  2009. ValueError: No JSON object could be decoded
  2010. 04.06.2018 00:24:56, mini - EOS Argentina [@moonxor]: you need to update the eosio plugin
  2011. 04.06.2018 00:25:25, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Hey mini why do we have to merge snaoshot-plugin
  2012. 04.06.2018 00:25:32, mini - EOS Argentina [@moonxor]: there was a problem with the plugin so we contacted the creator of the plugin, rebuild the nodeos with the latest changes
  2013. 04.06.2018 00:25:59, mini - EOS Argentina [@moonxor]: we use that plugin to take the snapshot :)
  2014. 04.06.2018 00:26:08, Nathan Rempel | GenerEOS Sydney [@nsrempel]: ok, so i was on eos-mainnet/eos tag v1.0.1 and applied git merge origin/snapshot-plugin
  2015. 04.06.2018 00:26:16, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: does the chain need that on mainnet?
  2016. 04.06.2018 00:26:38, Nathan Rempel | GenerEOS Sydney [@nsrempel]: although i hadn't pulled, perhaps missing some update
  2017. 04.06.2018 00:26:40, mini - EOS Argentina [@moonxor]: no you just need it for the validation, the endpoint dosent need that
  2018. 04.06.2018 00:27:09, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: So I am trying to understand this
  2019. 04.06.2018 00:27:11, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I need a local chain
  2020. 04.06.2018 00:27:15, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: to validate external chain?
  2021. 04.06.2018 00:27:19, mini - EOS Argentina [@moonxor]: for example, if we want to validate a chain booted by EOS Cafe, you dont need that plugin, we just run a nodeos with that plugin against your endpoint
  2022. 04.06.2018 00:27:28, mini - EOS Argentina [@moonxor]: no, a local nodeos
  2023. 04.06.2018 00:27:46, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: [[🐻 Sticker, size 39'322 bytes]]
  2024. 04.06.2018 00:27:50, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: ofcourse, thank you!
  2025. 04.06.2018 00:28:08, mini - EOS Argentina [@moonxor]: no man , no problem! we didnt document anything, sorry
  2026. 04.06.2018 00:28:09, Nathan Rempel | GenerEOS Sydney [@nsrempel]: was hoping it would be a little faster on the machine itself haha
  2027. 04.06.2018 00:28:37, mini - EOS Argentina [@moonxor]: the replay is the problem
  2028. 04.06.2018 00:28:41, mini - EOS Argentina [@moonxor]: :(
  2029. 04.06.2018 00:28:54, Nathan Rempel | GenerEOS Sydney [@nsrempel]: ok i'll try running it local
  2030. 04.06.2018 00:29:03, Nathan Rempel | GenerEOS Sydney [@nsrempel]: with the latest snapshot merge
  2031. 04.06.2018 00:29:10, mini - EOS Argentina [@moonxor]: we cant do anything with that, but if alex or anyone launching use our firestarter injection technique, we could all enjoy some speed :D
  2032. 04.06.2018 01:00:40, mini - EOS Argentina [@moonxor]: ok, i added some stuff to the validator, you now can run everything with arguments, and it shows you the eos.log file instead of the sad waitin message
  2033. 04.06.2018 01:03:31, mini - EOS Argentina [@moonxor]: so, if you want to validate a chain the steps are
  2034.  
  2035. 1- inside /firestarter/validator, create a folder with a name, ex ghost
  2036. 2- inside ghost put your genesis and snapshot files
  2037. 3- run
  2038. ./validate_chain_at_block.sh \
  2039. --network=ghost \
  2040. --block= < block_id> \
  2041. --p2p=<endpoint_ip>:<endpoint_port>
  2042. 04.06.2018 02:08:33, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i get it going off with
  2043. 468008ms thread-0 producer_plugin.cpp:751 start_block ] Not producing block because I don't have the private key for EOS7m4uBgRXBM5DbXFX7FTrNiZyRzxfktmto6qQTzc2z3BhgAGHKM
  2044. 04.06.2018 02:08:58, Nathan Rempel | GenerEOS Sydney [@nsrempel]: thats the initial key in the genesis
  2045. 04.06.2018 02:11:54, mini - EOS Argentina [@moonxor]: You run the./boot.sh with the default config?
  2046. 04.06.2018 02:12:16, Nathan Rempel | GenerEOS Sydney [@nsrempel]: im not trying to boot
  2047. 04.06.2018 02:12:36, Nathan Rempel | GenerEOS Sydney [@nsrempel]: ./validate_chain_at_block.sh —network=eos —block=000017dee519f1785e571480fe72989ac2dc7e4d00ecd0aa925aba6e7af414e4 —p2p=p2p.genereos.io:9876
  2048. 04.06.2018 02:13:00, Nathan Rempel | GenerEOS Sydney [@nsrempel]: just a remote validate
  2049. 04.06.2018 02:13:46, mini - EOS Argentina [@moonxor]: The validator shouldnt produce blocks, im in a cab right now let me get home and i take a look at it
  2050. 04.06.2018 02:13:55, Nathan Rempel | GenerEOS Sydney [@nsrempel]: cool man
  2051. 04.06.2018 02:18:53, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i might have figured it
  2052. 04.06.2018 02:19:09, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i had a config file at the default macOS location that might have been loading a config.ini
  2053. 04.06.2018 02:19:16, Nathan Rempel | GenerEOS Sydney [@nsrempel]: removed it... seems to be ok now
  2054. 04.06.2018 02:26:34, mini - EOS Argentina [@moonxor]: great! would you like to report an issue to our repo? I think validating full macOS compatibility would be awesome.
  2055. 04.06.2018 02:27:15, Nathan Rempel | GenerEOS Sydney [@nsrempel]: sure can do
  2056. 04.06.2018 02:27:58, mini - EOS Argentina [@moonxor]: thanks!
  2057. 04.06.2018 02:30:43, Nathan Rempel | GenerEOS Sydney [@nsrempel]: getting block now 🤞
  2058. 04.06.2018 02:32:04, mini - EOS Argentina [@moonxor]: :D
  2059. 04.06.2018 02:32:31, mini - EOS Argentina [@moonxor]: depending on the chain, its going to take a short or long amount of time, but at least you can see the blocks comming :)
  2060. 04.06.2018 02:32:47, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 3000/6000 haha
  2061. 04.06.2018 02:34:27, mini - EOS Argentina [@moonxor]: \o/
  2062. .....04.06.2018 02:37:49, jem [@jemxpat]: >>invited Timothy Lewis [@trustlayer]<<
  2063. 04.06.2018 02:41:42, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Snapshot saved in /Users/nathan.rempel/firestarter/validator/this/files/snapshot.bin
  2064. Converting snapshot to json ...
  2065. Validating EOS blockchain snapshot against "EOS Vanilla validator (v0.1)"
  2066. Loading EOS snapshot OK
  2067. Loading ETH snapshot OK
  2068. Load EOS genesis OK
  2069. Validating genesis FAIL
  2070. > please check /var/folders/xg/vmswb7md08l3rcf0kjkq973j_h0nqb/T/tmpWLYS9v for details
  2071. Verifying global params vs genesis OK
  2072. Verifying user account creation OK
  2073. Verifying user account stake OK
  2074. Verifying user account code OK
  2075. Verifying user account permission OK
  2076. Verifying privileged accounts OK
  2077. Verifying extra accounts FAIL
  2078. > Extra account found guztqobqgqge
  2079. > Extra account found eosio.burned
  2080. > Extra account found eosio.unregd
  2081. > Extra account found gqytcmrrgige
  2082. 04.06.2018 02:42:19, Nathan Rempel | GenerEOS Sydney [@nsrempel]: very cool
  2083. 04.06.2018 02:46:12, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i copied snapshot.csv from eosbios-stage20 and got Validating EOS blockchain snapshot against "EOS Vanilla validator (v0.1)"
  2084. Loading EOS snapshot OK
  2085. Loading ETH snapshot OK
  2086. Load EOS genesis OK
  2087. Validating genesis FAIL
  2088. > please check /var/folders/xg/vmswb7md08l3rcf0kjkq973j_h0nqb/T/tmpqZbpWb for details
  2089. Verifying global params vs genesis OK
  2090. Verifying user account creation OK
  2091. Verifying user account stake OK
  2092. Verifying user account code OK
  2093. Verifying user account permission OK
  2094. Verifying privileged accounts OK
  2095. Verifying extra accounts FAIL
  2096. > Extra account found eosio.burned
  2097. > Extra account found eosio.unregd
  2098. 04.06.2018 02:46:41, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: eosbios-stage20 snapshot is not the final snapshot
  2099. 04.06.2018 02:47:08, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I understand, just cool to see the difference
  2100. .....04.06.2018 03:10:32, lo chaiching [@lochaiching]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2101. 04.06.2018 03:12:48, Sukesh Tedla (EOSGreen) [@Sukeshtedla]: [[Webpage]]Hi Guys, I have been actively monitoring the news and this is not to mock anyone. I just read this article, I know everyone is busy but it's worth a while reading and maybe reacting on it: https://www.trustnodes.com/2018/06/03/just-10-addresses-hold-nearly-50-eos-tokens
  2102. 04.06.2018 03:17:45, mini - EOS Argentina [@moonxor]: ❤️❤️❤️, it was easy right?
  2103. 04.06.2018 03:28:32, Timothy Lewis [@trustlayer]: [[Webpage]]I would like to gather approval for VULN testing by BPC administrators.
  2104.  
  2105. Please fill the BP tab on the spreadsheet to acknoledge testing acceptance.
  2106.  
  2107. https://docs.google.com/spreadsheets/d/1dgmt_Hk5lqhxkvC5yv9lApzogPlUzQE9QItB15UYprk/edit?usp=sharing
  2108.  
  2109. Please join the EOSIO Security discussion:
  2110. https://t.me/joinchat/FTzsFlKJbwM5wXHeLKP9gA
  2111.  
  2112. EOSIO SECURITY CALL FOR DISCOVERY AT 12:00 UTC
  2113. .....04.06.2018 04:40:27, Jack - AcroEOS [@gjacklee]: >>invited Moon@Acroeos [@moonlightbp]<<
  2114. 04.06.2018 04:41:00, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I read it, it’s a BS article - we are too busy to react to this type of stuff.
  2115. 04.06.2018 04:43:02, Sukesh Tedla (EOSGreen) [@Sukeshtedla]: I agree. Just wanted to share it. I appreciate all the efforts from each and everyone. Thanks for the great work you guys are doing.
  2116. 04.06.2018 04:44:37, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We have a test plan pinned to this group , can I suggest that you add your suggestion for testing to it, and try make a case for it on our 13:00 UTC call
  2117.  
  2118. I could see why each BP may or may not want to take part, but I’m not sure it is relevant to chain validation.
  2119. 04.06.2018 04:47:05, Timothy Lewis [@trustlayer]: It has absolute relevance. We are coordinating with a large group of BPCs now in the EOSIO security channel. We have multiple indipendant security groups testing and will share our results during the 13:00 call.
  2120. 04.06.2018 04:47:27, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: isnt the call at 12:00?
  2121. 04.06.2018 04:47:33, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: the security one atleast
  2122. 04.06.2018 04:47:41, Timothy Lewis [@trustlayer]: Correct, the security call will be 12:00
  2123. 04.06.2018 04:51:57, Timothy Lewis [@trustlayer]: EOSIO Security channel: https://t.me/joinchat/FTzsFlKJbwM5wXHeLKP9gA
  2124. 04.06.2018 08:27:02, deck - EOS New York [@deckw]: My output differed slightly:
  2125. Converting snapshot to json ...
  2126. Validating EOS blockchain snapshot against "EOS Vanilla validator (v0.1)"
  2127. Loading EOS snapshot OK
  2128. Loading ETH snapshot OK
  2129. Load EOS genesis OK
  2130. Validating genesis FAIL
  2131. > please check /tmp/tmpeGTk3G for details
  2132. Verifying global params vs genesis FAIL
  2133. > Unable to compare global params, initial_configuration not found in genesis
  2134. Verifying user account creation OK
  2135. Verifying user account stake OK
  2136. Verifying user account code OK
  2137. Verifying user account permission OK
  2138. Verifying privileged accounts OK
  2139. Verifying extra accounts FAIL
  2140. > Extra account found guztqobqgqge
  2141. > Extra account found eosio.burned
  2142. > Extra account found eosio.unregd
  2143. > Extra account found gqytcmrrgige
  2144. 04.06.2018 08:35:00, Alexandre Bourget - EOS Canada [@abourget]: which chain_id ? and what is your snapshot reference ?
  2145. 04.06.2018 08:35:20, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: The one provided in stage20 snapshot folder
  2146. 04.06.2018 08:35:24, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: In firestarter
  2147. 04.06.2018 08:35:58, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Does not match with the consensus snapshot, can check again
  2148. 04.06.2018 08:36:07, Alexandre Bourget - EOS Canada [@abourget]: @moonxor so snapshot validation of chain 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5 failed ?!
  2149. 04.06.2018 08:36:59, Alexandre Bourget - EOS Canada [@abourget]: The snapshot used was https://github.com/eoscanada/eos-bios/blob/master/sample_config/my_discovery_file.yaml#L56
  2150. 04.06.2018 08:37:30, Alexandre Bourget - EOS Canada [@abourget]: Can you confirm it's a different one ? I haven't seen any newer one
  2151. 04.06.2018 08:39:09, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I checked against
  2152. firestarter/validator/eosbios-stage20/snapshot.csv
  2153. 04.06.2018 08:39:26, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Not on chain
  2154. 04.06.2018 08:41:26, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: That one is correct
  2155. 04.06.2018 08:41:33, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I dont know what they have in their folder
  2156. 04.06.2018 08:43:25, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Excellent work so far on Validation. We will be starting our call in 20 mins - 13:00 UTC
  2157.  
  2158. I will post Zoom here in 10 mins.
  2159. 04.06.2018 08:56:13, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]https://zoom.us/j/551514141
  2160. 04.06.2018 09:11:52, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: The sha256 hash of the snapshot.csv used is 6df61f12f96f89c907fac14a021d788c9e77098952a6c5494c7999d2e79d0a35
  2161. 04.06.2018 09:16:15, Alexandre Bourget - EOS Canada [@abourget]: CHAIN ID: 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5
  2162. 04.06.2018 09:16:23, Denis | EOS Nation [@DenisCarriere]: {{FWD: Alexandre Bourget - EOS Canada [@abourget], 03.06.2018 11:54:00}}
  2163. To those nearby, can you provide with a p2p endpoints, setup with the following genesis.json:
  2164. {"initial_timestamp":"2018-06-03T13:04:31","initial_key":"EOS7m4uBgRXBM5DbXFX7FTrNiZyRzxfktmto6qQTzc2z3BhgAGHKM"}
  2165.  
  2166. * Chain ID: 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5
  2167. * Genesis JSON: {"initial_timestamp":"2018-06-03T13:04:31","initial_key":"EOS7m4uBgRXBM5DbXFX7FTrNiZyRzxfktmto6qQTzc2z3BhgAGHKM"}
  2168. * Resignation block: 2683
  2169. * Frozen head block: 6110
  2170.  
  2171. Another RC chain is ready, I'll peer it out for validation. I'll do a better announcement in a short while.
  2172.  
  2173. v1.0.1
  2174. .....04.06.2018 10:08:14, cupide EOS Pacific: >>unsupported service message type: messageActionChatJoinedByLink<<
  2175. .....04.06.2018 10:08:40, Jacky - JEDA [@newbdez33]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2176. .....04.06.2018 10:09:48, Mark-eosantpool [@mark_cike]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2177. .....04.06.2018 10:13:11, Mathieu Boulianne - EOS Canada [@mathieubo]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2178. .....04.06.2018 10:13:37, zhangzc | Onechain [@zhangzc]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2179. .....04.06.2018 10:14:39, [email protected] [@crazybits]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2180. .....04.06.2018 10:16:17, Ren Kaidi - EOSWTZ [@FoxMr]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2181. .....04.06.2018 10:21:54, kenneth: >>unsupported service message type: messageActionChatJoinedByLink<<
  2182. .....04.06.2018 10:21:55, Jason Wang - EOS Pacific [@jason_wang_4595]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2183. .....04.06.2018 10:22:06, Ville Sundell [@SolariusFI]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2184. .....04.06.2018 10:22:21, Elliot@EOS Pacific [@Elliot521]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2185. .....04.06.2018 10:24:14, Discha W [@afeidischa]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2186. .....04.06.2018 10:28:34, Che Hao Yang [@hankych]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2187. .....04.06.2018 10:30:47, Joshua Qiu @EOSeco [@Joshuaqiu]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2188. .....04.06.2018 10:31:11, Angelo Wang: >>unsupported service message type: messageActionChatJoinedByLink<<
  2189. 04.06.2018 10:45:29, Sam - EOS Dublin [@samnoble]: Dear all, thanks again for another productive call. I think we can all agree we're another step closer to a successful and secure EOS launch. Whilst it might seem slow and frustrating, just take a second to think about the scale of what we're doing here. As a quick re-cap:
  2190.  
  2191. - Alex (@abourget) from EOS Canada will now work to push out a new test net and release the private key via the validation channel. Everyone is then free (and encouraged) to use this to create their own test nets
  2192. - Alex from EOS Canada will modify the duration for which tokens are staked to reduce the lock in time to expedite testing. This will NOT be loaded in to the new test net and will be optional for people to load in to their own net
  2193. - Jem (@jemxpat) will run point on this and will facilitate communication with the Ghostbusters team
  2194. - The Ghostbusters team will mesh in to the new network to ensure crossover
  2195. - Everyone will now conduct their own testing either on one of the existing test nets, or one they stand up themselves with the view to using the validation plan as a reference in order to perform their own validation testing of the platform.
  2196. - We should be working towards a position where each BP is satisfied that the current version of the platform is ready for prime time, to launch the main net (pending feedback from the security testing). This will be in the form of some kind of joint statement, TBD.
  2197. - We'll reconvene at 1300 UTC Tuesday June 5th
  2198. - Ben (@Bensig) will work on a public statement that we’ll release to keep the community abreast of the situation.
  2199.  
  2200. We’ll use this channel for coordination.
  2201. 04.06.2018 11:05:37, Josh Kauffman - EOS Canada [@joshkauff]: Just wanted to check and try to grab a more global consensus from BPs. The contents of the chain that was spun up yesterday (chain id: 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5), do we all agree upon it containing the correct information (constitution, ricardians, snapshot, source code...)? Want to ensure we're all on the same page.
  2202. 04.06.2018 11:06:58, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 👍
  2203. 04.06.2018 11:07:11, Nathan Rempel | GenerEOS Sydney [@nsrempel]: We confirmed
  2204. 04.06.2018 11:07:40, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Although, does it have the very latest ricardian updates?
  2205. 04.06.2018 11:10:05, mini - EOS Argentina [@moonxor]: we didnt test for everything in the spread sheet yet. Was looking good for sure.
  2206. 04.06.2018 11:12:23, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Have we agreed on a specific commit to launch with?
  2207. 04.06.2018 11:12:29, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Should we release a launch tag
  2208. 04.06.2018 11:12:55, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: People seem to be pulling v1.0.1 and adding consitution/etc from governance repo
  2209. 04.06.2018 11:13:06, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: That may not line up like a release tag
  2210. .....04.06.2018 11:18:29, Bonnie Wang [@eostarkBP]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2211. 04.06.2018 11:22:53, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I think we need a Launch Tag
  2212. 04.06.2018 11:24:30, James Sutherland - Cypherglass.com [@JamesSutherland]: +1
  2213. 04.06.2018 11:25:19, Guillaume @eostitan.com [@gyom_eos_titan]: agreed
  2214. .....04.06.2018 11:25:52, [email protected] [@PennyYip]: >>unsupported service message type: messageActionChatJoinedByLink<<
  2215. .....04.06.2018 11:27:18, skep: >>unsupported service message type: messageActionChatJoinedByLink<<
  2216. 04.06.2018 11:29:02, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Also agree
  2217. 04.06.2018 11:31:16, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Have asked in the right channel for that to happen
  2218. 04.06.2018 11:35:00, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: A launch tag is being worked on by Cesar!
  2219. 04.06.2018 11:45:37, Denis | EOS Nation [@DenisCarriere]: By any chance, could we start this next call earlier (proposing 1200 UTC). We could divide the meeting into two parts, first hour can be discussions of validation/testing and 2nd part would be taking/making the decisions. That way if BP's cannot be there for the validation discussion, they can easily join in on the "action" part.
  2220.  
  2221. 1200 UTC (validation/security phase)
  2222. First hour to discussing our validation/testing/security findings
  2223.  
  2224. 1300 UTC (action phase)
  2225. Decide if we have a mainnet candidate:
  2226. - IF TRUE => Launch mainnet candidate and open a limited amount of API endpoints
  2227. - IF FALSE => Define which validation steps failed & propose another meeting in +24 hours
  2228. 04.06.2018 11:46:23, Craig Murray - EOS BlockSmith [@craigmurray100]: just coordinate with the security channel where the earlier of the two meetings is organized
  2229. 04.06.2018 11:46:35, Craig Murray - EOS BlockSmith [@craigmurray100]: im all for it being 1 call 👍
  2230. 04.06.2018 11:47:23, Denis | EOS Nation [@DenisCarriere]: Yes the security discussion could happen on the first hour (1200 UTC), that way we have a good "flow" during the meeting and not have people drop off to join other Zoom video calls
  2231. 04.06.2018 11:48:44, mini - EOS Argentina [@moonxor]: i rather continue with 1300 utc, but if everyone is on board I can make it to 1200 , but is one hour less of sleep for me :P
  2232. 04.06.2018 12:07:31, Alexandre Bourget - EOS Canada [@abourget]: ALL:
  2233.  
  2234. I'm currently injecting the test run, without resignation.
  2235.  
  2236. Genesis JSON: {"initial_timestamp":"2018-06-04T15:31:02","initial_key":"EOS8VtXjprEnsyzyGbo7xXCjcE4omxKhEv5bkJkjUkefHQ84b2j5A"}
  2237.  
  2238. I'll peer it out for people to observe. I would appreciate at least 3 peers to swarm the blocks out.
  2239. 04.06.2018 12:12:00, Niclas Hedhman - EOS Germany [@niclash]: You mean regular full nodes to connect?
  2240. 04.06.2018 12:12:29, Alexandre Bourget - EOS Canada [@abourget]: Yes.. not ones participating in yesterday,s chain..
  2241. 04.06.2018 12:12:36, Alexandre Bourget - EOS Canada [@abourget]: The testnet chain_id is 050ca7388c8b3a394e8c5cf817600cec5f2235c31dc37a2596522e934cf988c0
  2242. 04.06.2018 12:12:53, Joshua Qiu @EOSeco [@Joshuaqiu]: validation.eoseco.com:10020
  2243. 04.06.2018 12:12:54, Alexandre Bourget - EOS Canada [@abourget]: ok, local validation passed.. I'll peer that out now
  2244. 04.06.2018 12:12:55, Alexandre Bourget - EOS Canada [@abourget]: Anyone ready ?
  2245. 04.06.2018 12:13:00, Alexandre Bourget - EOS Canada [@abourget]: Great! Thanks Joshua!
  2246. 04.06.2018 12:13:11, Joshua Qiu @EOSeco [@Joshuaqiu]: your address?
  2247. 04.06.2018 12:13:14, Jacky - JEDA [@newbdez33]: m.jeda.one:3322
  2248. 04.06.2018 12:13:53, Jacky - JEDA [@newbdez33]: just restart my node with new genesis
  2249. 04.06.2018 12:15:39, Alexandre Bourget - EOS Canada [@abourget]: ready ?
  2250. 04.06.2018 12:15:43, Jacky - JEDA [@newbdez33]: yes
  2251. 04.06.2018 12:15:53, Nate D - Aloha EOS [@n8dee]: I'm ready too: peer2.test.alohaeos.com:9876
  2252. 04.06.2018 12:17:13, Jacky - JEDA [@newbdez33]: {"server_version":"0961a560","chain_id":"050ca7388c8b3a394e8c5cf817600cec5f2235c31dc37a2596522e934cf988c0","head_block_num":1,"last_irreversible_block_num":0,
  2253. 04.06.2018 12:17:34, Niclas Hedhman - EOS Germany [@niclash]: I now require "known IP numbers" on the p2p port.
  2254. 04.06.2018 12:18:34, Nate D - Aloha EOS [@n8dee]: allow my host above and I'll peer to you
  2255. 04.06.2018 12:19:02, Nate D - Aloha EOS [@n8dee]: I'm just using a test host
  2256. 04.06.2018 12:20:20, Alexandre Bourget - EOS Canada [@abourget]: Tell me when you get blocks.
  2257. 04.06.2018 12:20:33, Nate D - Aloha EOS [@n8dee]: getting blocks 👍
  2258. 04.06.2018 12:20:45, Jacky - JEDA [@newbdez33]: getting it
  2259. 04.06.2018 12:20:46, Alexandre Bourget - EOS Canada [@abourget]: it's a locked-down chain now..I'll post the private key when you're all past the "pre-resignation" block :)
  2260. .....04.06.2018 12:20:49, Jack - AcroEOS [@gjacklee]: >>invited Myoungchul Park [@sps818]<<
  2261. 04.06.2018 12:21:58, James Sutherland - Cypherglass.com [@JamesSutherland]: 12:00UTC is 5am Pacific time, those of us on the west coast of the US woudl appricate 13:00 or later.
  2262. 04.06.2018 12:22:20, Joshua Qiu @EOSeco [@Joshuaqiu]: make sure , we will give up this chain after validation
  2263. 04.06.2018 12:22:22, Joshua Qiu @EOSeco [@Joshuaqiu]: ?
  2264. 04.06.2018 12:26:52, James Sutherland - Cypherglass.com [@JamesSutherland]: My node is up @ publicnode.cypherglass.com:9876
  2265. 04.06.2018 12:26:57, James Sutherland - Cypherglass.com [@JamesSutherland]: It's syncing
  2266. 04.06.2018 12:27:28, Joshua Qiu @EOSeco [@Joshuaqiu]: syncing
  2267. 04.06.2018 12:27:46, James Sutherland - Cypherglass.com [@JamesSutherland]: 1000
  2268. 04.06.2018 12:29:44, Jacky - JEDA [@newbdez33]: cleos.sh get info
  2269. {
  2270. "server_version": "0961a560",
  2271. "chain_id": "579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5",
  2272. "head_block_num": 6110,
  2273. "last_irreversible_block_num": 6109,
  2274. "last_irreversible_block_id": "000017dd169a1f50a4808f3563517cc1df881a16776a6d9a91e544e0fc31e782",
  2275. "head_block_id": "000017dee519f1785e571480fe72989ac2dc7e4d00ecd0aa925aba6e7af414e4",
  2276. "head_block_time": "2018-06-03T17:36:41",
  2277. "head_block_producer": "eosio",
  2278. "virtual_block_cpu_limit": 735929,
  2279. "virtual_block_net_limit": 472963532,
  2280. "block_cpu_limit": 199900,
  2281. "block_net_limit": 1048576
  2282. }
  2283. 04.06.2018 12:30:18, Nate D - Aloha EOS [@n8dee]: that's a different chain id than I have
  2284. 04.06.2018 12:30:58, Nate D - Aloha EOS [@n8dee]: {
  2285. "server_version": "1314e925",
  2286. "chain_id": "050ca7388c8b3a394e8c5cf817600cec5f2235c31dc37a2596522e934cf988c0",
  2287. "head_block_num": 4791,
  2288. "last_irreversible_block_num": 4790,
  2289. "last_irreversible_block_id": "000012b6de601b2863cf74cec413781b00b671d2ed0b5d72f721b5955656abe5",
  2290. "head_block_id": "000012b7bd12ee04ba08fba8e2f2ac0ece9154cbfcdc8607feb1ee1aec56d63b",
  2291. "head_block_time": "2018-06-04T16:14:37",
  2292. "head_block_producer": "eosio",
  2293. "virtual_block_cpu_limit": 325576,
  2294. "virtual_block_net_limit": 126388596,
  2295. "block_cpu_limit": 199900,
  2296. "block_net_limit": 1048576
  2297. }
  2298. 04.06.2018 12:31:00, Jacky - JEDA [@newbdez33]: Sorry. mistake. the correct one is : 050ca7388c8b3a394e8c5cf817600cec5f2235c31dc37a2596522e934cf988c0
  2299. 04.06.2018 12:31:07, Nate D - Aloha EOS [@n8dee]: oh ok, cool
  2300. 04.06.2018 12:31:19, Nate D - Aloha EOS [@n8dee]: and we seem to have paused at 4791
  2301. 04.06.2018 12:31:24, James Sutherland - Cypherglass.com [@JamesSutherland]: Chain Id
  2302. 050ca7388c8b3a394e8c5cf817600cec5f2235c31dc37a2596522e934cf988c0
  2303. 04.06.2018 12:35:59, Alexandre Bourget - EOS Canada [@abourget]: it's not paused, it's flowing though..
  2304. 04.06.2018 12:36:00, Alexandre Bourget - EOS Canada [@abourget]: 7338
  2305. 04.06.2018 12:36:29, Nate D - Aloha EOS [@n8dee]: I must have lost connectivity then
  2306. 04.06.2018 12:36:55, James Sutherland - Cypherglass.com [@JamesSutherland]: Yea me too, been stuck for a while ~1000
  2307. 04.06.2018 12:37:32, Joshua Qiu @EOSeco [@Joshuaqiu]: yes , first sycing is slow
  2308. 04.06.2018 12:37:44, Joshua Qiu @EOSeco [@Joshuaqiu]: you can see that cpu usage is 100%
  2309. 04.06.2018 12:39:47, Alexandre Bourget - EOS Canada [@abourget]: Aloha, you still connected ?
  2310. 04.06.2018 12:40:05, Alexandre Bourget - EOS Canada [@abourget]: I'll stop production.. it,s not useful to move it forward anyway
  2311. 04.06.2018 12:40:17, Nate D - Aloha EOS [@n8dee]: I'm still at 4791 height
  2312. 04.06.2018 12:41:26, Alexandre Bourget - EOS Canada [@abourget]: Aloha I lost connection to you for a moment...
  2313. 04.06.2018 12:41:37, Alexandre Bourget - EOS Canada [@abourget]: connection failed to peer2.test.alohaeos.com:9876: Connection refused
  2314. 04.06.2018 12:41:46, Nate D - Aloha EOS [@n8dee]: I restarted breifly to add peers but it's back now
  2315. 04.06.2018 12:43:11, James Sutherland - Cypherglass.com [@JamesSutherland]: 3000
  2316. 04.06.2018 12:43:19, Jacky - JEDA [@newbdez33]: i'm on 4791
  2317. 04.06.2018 12:43:56, Joshua Qiu @EOSeco [@Joshuaqiu]: me too
  2318. 04.06.2018 12:46:36, James Sutherland - Cypherglass.com [@JamesSutherland]: 4791
  2319. 04.06.2018 12:46:51, James Sutherland - Cypherglass.com [@JamesSutherland]: CPU down to idle now
  2320. 04.06.2018 12:47:25, Joshua Qiu @EOSeco [@Joshuaqiu]: maybe stop producing
  2321. 04.06.2018 12:49:40, Jacky - JEDA [@newbdez33]: if stop producing we can still sync to the latest blocks right?
  2322. 04.06.2018 12:53:31, Nate D - Aloha EOS [@n8dee]: I'm at 6110 now
  2323. 04.06.2018 12:54:47, Robert DeWilder - Worbli [@BrownDonahue]: worbli is up @ validation-1.worbli.io:33981 and syncing
  2324. 04.06.2018 12:55:14, Robert DeWilder - Worbli [@BrownDonahue]: Are you still stuck ~1000?
  2325. 04.06.2018 12:55:22, Robert DeWilder - Worbli [@BrownDonahue]: I am seeing the same
  2326. 04.06.2018 12:55:28, James Sutherland - Cypherglass.com [@JamesSutherland]: I'm holding at 4791 now
  2327. 04.06.2018 12:55:33, Joshua Qiu @EOSeco [@Joshuaqiu]: just wait
  2328. 04.06.2018 12:55:40, Joshua Qiu @EOSeco [@Joshuaqiu]: me too
  2329. 04.06.2018 12:55:41, Jose Toriello [@josetoriello]: Maybe pin this?
  2330. 04.06.2018 12:56:31, Nate D - Aloha EOS [@n8dee]: Sorry, I looked at the wrong window (too many open). I'm still at 4791 as well.
  2331. 04.06.2018 12:57:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Let’s keep to 13:00 UTC for call tomorrow.
  2332.  
  2333. I actually propose we have a standing call at that time for BPs through launch and possibly after also.
  2334.  
  2335. BP Communication is going to be critical.
  2336. 04.06.2018 12:59:00, deck - EOS New York [@deckw]: +1
  2337. .....04.06.2018 13:01:23, Myoungchul Park [@sps818]: >>invited J Y [@y30nj]<<
  2338. 04.06.2018 13:15:12, mini - EOS Argentina [@moonxor]: +1
  2339. 04.06.2018 13:18:49, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: I don't understand why we don't aks everyone in the eosio-bios-boot group to join? Some people have previous chain, some people have this chain. Is there a reason to maintain the old one?
  2340. .....04.06.2018 13:21:54, Ben Sigman [@Bensig]: >>invited David Moss [@DavidMoss]<<
  2341. .....04.06.2018 13:22:56, Ben Sigman [@Bensig]: >>invited Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]<<
  2342. 04.06.2018 13:47:47, mini - EOS Argentina [@moonxor]: [[Webpage]]https://www.reddit.com/r/eos/comments/8oikln/eos_nation_weve_booted_the_mainnet_and_entered/
  2343. 04.06.2018 13:49:11, Ville Sundell [@SolariusFI]: @stuardo_str I have understood, that the 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5 is still the candidate for the mainnet?
  2344. 04.06.2018 13:49:33, David P - EOS42 [@GunnisonCap]: Hmm is that technically true? 🤔
  2345. 04.06.2018 13:50:05, Rick Schlesinger - EOS New York [@unlockrs]: seems a bit premature...
  2346. 04.06.2018 13:50:47, nahu [@naueh]: find it disrespectful to the community, at least
  2347. 04.06.2018 13:51:00, Timothy Lewis [@trustlayer]: I thought we had agreed to coordinate comms and work collaboratively.
  2348. 04.06.2018 13:51:20, mini - EOS Argentina [@moonxor]: I'm not on EOS naton :)
  2349. 04.06.2018 13:51:42, mini - EOS Argentina [@moonxor]: Just Saw that and put it here
  2350. 04.06.2018 13:51:51, Timothy Lewis [@trustlayer]: copy
  2351. 04.06.2018 13:52:00, mini - EOS Argentina [@moonxor]: And paste :)
  2352. 04.06.2018 13:52:10, Timothy Lewis [@trustlayer]: Who is the EOS Nation contact?
  2353. 04.06.2018 13:52:18, mini - EOS Argentina [@moonxor]: @DenisCarriere
  2354. 04.06.2018 13:54:26, mini - EOS Argentina [@moonxor]: @stuardo_str Also i think
  2355. 04.06.2018 13:54:33, Denis | EOS Nation [@DenisCarriere]: This was a miscommunication, we've removed this Tweet immediately.
  2356.  
  2357. This has been copied by another user.
  2358.  
  2359. It should of said => "We're testing v1.0 and are currently in the validation stage"
  2360.  
  2361. 😢
  2362.  
  2363. The wording was misused, the intent of EOS Nation was never to say "we've launched mainnet", we have ZERO endpoints opened to the public.
  2364. 04.06.2018 13:55:19, nahu [@naueh]: thanks for the clarification
  2365. 04.06.2018 13:55:27, Timothy Lewis [@trustlayer]: We agreed in validation to coordinate comms
  2366. 04.06.2018 13:55:37, Timothy Lewis [@trustlayer]: Thank you for cleaning it up quickly.
  2367. 04.06.2018 13:56:39, Denis | EOS Nation [@DenisCarriere]: I've been radio silence with our "social media/marketing" team, however I guess they misunderstood the message.
  2368.  
  2369. Everyone does know we are still in the "testing/validation" stages, we shouldn't of mentioned the word "mainnet"
  2370. 04.06.2018 13:57:33, Denis | EOS Nation [@DenisCarriere]: [[Photo]]On our homepage, we have "Testing in progress"
  2371.  
  2372. https://eosnation.io
  2373. 04.06.2018 13:57:48, Timothy Lewis [@trustlayer]: Crafting a voice from the combined efforts of the BPC community is important. we will release a guideline for testing expectations.
  2374. 04.06.2018 14:01:14, Denis | EOS Nation [@DenisCarriere]: Another issue is the EOSGo countdown, we might want to remove this as well:
  2375.  
  2376. http://eosgo.io/6626-2/
  2377. 04.06.2018 14:02:32, Denis | EOS Nation [@DenisCarriere]: [[Photo]]09 hours will not be when voting happens (not to my knowledge from this group)
  2378. 04.06.2018 14:03:59, David P - EOS42 [@GunnisonCap]: No problem and thanks for removing. Let’s keep the communication coordinated all so we don’t confuse the community inadvertently.
  2379. 04.06.2018 14:04:07, Denis | EOS Nation [@DenisCarriere]: The more we drag our feet with this validation, the MORE incorrect messages will arise in the future.
  2380.  
  2381. Let's make sure at our next call we've got some solid validation results
  2382. .....04.06.2018 14:07:25, Timothy Lewis [@trustlayer]: >>invited Kedar Iyer | LibertyBlock [@k26dr]<<
  2383. 04.06.2018 14:16:27, Mathieu Boulianne - EOS Canada [@mathieubo]: They now fixed the countdown on their website
  2384. 04.06.2018 14:18:29, Denis | EOS Nation [@DenisCarriere]: Perfect! 👍we are all working together on this, one big team
  2385. 04.06.2018 14:19:38, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Indeed!
  2386. 04.06.2018 14:20:55, David Moss [@DavidMoss]: {{FWD: David Moss [@DavidMoss], 04.06.2018 14:16:51}}
  2387. Hey everyone! I'm excited about the launch and have been following all the different groups working on getting the EOSIO mainnet up and running. We at least need to get a test mainnet up and running as the world is watching. At this point I'd recommend that everyone connect to the EOS Core aka Ghostbusters chain so we can at least have a working mainnet even if it is a test. They are posting chain-specific information like the genesis info in their keybase group.
  2388. 04.06.2018 14:21:01, David Moss [@DavidMoss]: Cross-posting this.
  2389. 04.06.2018 14:26:47, Ville Sundell [@SolariusFI]: Is the Alex chain from yesterday (579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5) is still the/a candidate for the mainnet?
  2390. 04.06.2018 14:28:52, Craig Murray - EOS BlockSmith [@craigmurray100]: i suggest wording is "main net candidate" in all cases, or better, candidate
  2391. 04.06.2018 14:29:10, Timothy Lewis [@trustlayer]: Absolutely agreed.
  2392. 04.06.2018 14:29:16, Craig Murray - EOS BlockSmith [@craigmurray100]: we have a mainnet *candidate* right now, paused from about 28 hours ago, undergoing testing
  2393. 04.06.2018 14:29:54, Craig Murray - EOS BlockSmith [@craigmurray100]: we have further created a full test version, which is NOT a candidate, and where the god account is still active. This is being used by multiple groups to test features that are only present once we hit 15%, which we cannot test on the candidate directly
  2394. 04.06.2018 14:30:36, Craig Murray - EOS BlockSmith [@craigmurray100]: finally we are also creating a 2nd test version (not a candidate) where the unstaking timer is very small, so that it can be tested as well for unstaking after 15% without waiting 3 days to run the test
  2395. 04.06.2018 14:31:19, Craig Murray - EOS BlockSmith [@craigmurray100]: i would also suggest we stop talking about "eos-bios" and "ghostbusters" and "core". We are the mainnet launch group
  2396. 04.06.2018 14:31:25, Craig Murray - EOS BlockSmith [@craigmurray100]: we need to act like it
  2397. 04.06.2018 14:33:15, Sharif Bouktila - EOS Dublin [@sharifbouktila]: +1
  2398. 04.06.2018 14:35:18, Ville Sundell [@SolariusFI]: Thank you, this is the clarification I needed 🙂
  2399. 04.06.2018 14:37:26, Brett Jeffery @ EOS the World [@EOStheWorld]: 👏👏👏✔️
  2400. 04.06.2018 14:39:20, Denis | EOS Nation [@DenisCarriere]: 👏agreed, there should be no difference from the multiple launch groups, we're all going to be peering from the same chain_id. We can have different topologies, but at the end of the day, we're standing up 1 mainnet with the multiple launch groups strengthening the overall network
  2401. 04.06.2018 14:49:59, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: [[Webpage]]Guys, we are managed to test the unstaking mechanism in like 30 minutes.
  2402.  
  2403. We changed the unstaking delay from 3 days to 5 minutes.
  2404.  
  2405. We made a repo, to make sure that everyone can run an unstake test using your laptop.
  2406.  
  2407. and of course, the unstaking functionality works pretty well.
  2408.  
  2409. just give it a try: https://github.com/eoslaomao/eos-cluster-generator
  2410. 04.06.2018 14:50:49, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Great stuff 👍
  2411. 04.06.2018 14:52:40, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Very smart! Love it
  2412. 04.06.2018 14:52:48, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: time to bed, bye bye
  2413. 04.06.2018 15:00:27, Rick Schlesinger - EOS New York [@unlockrs]: +1
  2414. 04.06.2018 15:00:33, Rick Schlesinger - EOS New York [@unlockrs]: +1
  2415. 04.06.2018 15:01:35, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: +1 !! Well done...
  2416. 04.06.2018 15:04:43, deck - EOS New York [@deckw]: Super confused about what this article is trying to say? I thought we agreed to run software validation tests today and collectively communicate that out. This seems to imply that EOS Core is somehow ahead of the curve here.
  2417. 04.06.2018 15:04:43, deck - EOS New York [@deckw]: {{FWD: Ben Sigman [@Bensig], 04.06.2018 14:24:13}}
  2418. [[Webpage]]https://medium.com/@bensig/letter-to-eos-block-producer-candidates-184ef59a0748
  2419. 04.06.2018 15:48:52, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Guys I've cross posted our validation plan to the EOS core channel to give teams a framework for testing.
  2420.  
  2421. The objective is for multiple BPs to test and satisfy themselves we have a chain which can be proposed as Mainnet.
  2422.  
  2423. I don't believe that has changed since our call earlier.
  2424. 04.06.2018 15:53:56, deck - EOS New York [@deckw]: +1
  2425. 04.06.2018 16:00:16, mini - EOS Argentina [@moonxor]: great
  2426. 04.06.2018 17:51:24, nahu [@naueh]: May I ask if eos-bios and ghostbusters are still trying to rise the same blockchain?
  2427. 04.06.2018 17:52:53, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: Yes
  2428. 04.06.2018 18:21:19, Daniel Larimer [@daniellarimer]: [[Photo]]Are we there yet?
  2429. 04.06.2018 18:22:03, David Moss [@DavidMoss]: Getting closer...
  2430. 04.06.2018 18:22:21, Ben Sigman [@Bensig]: I would estimate that validation is going to take a few days - we added security validation and standards are being developed.
  2431. 04.06.2018 18:22:39, David Moss [@DavidMoss]: Ghostbusters is working on standing up a validated "test" mainnet.
  2432. 04.06.2018 18:22:40, mini - EOS Argentina [@moonxor]: it dosent take days :), takes minutes
  2433. 04.06.2018 18:23:26, Ben Sigman [@Bensig]: haha yes, on EOS Core/ghostbusters it's pretty straightforward
  2434. 04.06.2018 18:23:51, mini - EOS Argentina [@moonxor]: [[Photo]]
  2435. 04.06.2018 18:24:09, mini - EOS Argentina [@moonxor]: is the same for any chain., Tools to validate the state should be agnostic
  2436. 04.06.2018 18:24:30, mini - EOS Argentina [@moonxor]: this one is from core, a couple of minutes ago
  2437. 04.06.2018 18:24:46, Alexandre Bourget - EOS Canada [@abourget]: Did chain_id 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5 validate this ?
  2438.  
  2439. The chain we all have been working on since yesterday ?
  2440. 04.06.2018 18:24:48, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Why is stake different
  2441. 04.06.2018 18:25:08, mini - EOS Argentina [@moonxor]: i dont know, i think they have a rounding issue while injecting.
  2442. 04.06.2018 18:25:16, mini - EOS Argentina [@moonxor]: @deckw was the first to validate it
  2443. 04.06.2018 18:32:04, nahu [@naueh]: I'm not sure I understood. I'd support a main testnet though
  2444. 04.06.2018 19:19:32, Igor Lins e Silva - EOS Rio [@igorls]: @rbmarliere found it too
  2445. 04.06.2018 19:19:48, Ricardo Marlière - EOS Brazil [@rbmarliere]: hahaha
  2446. 04.06.2018 19:19:54, Igor Lins e Silva - EOS Rio [@igorls]: we are injecting again, real-time checks shows no error for now
  2447. 04.06.2018 19:20:17, Ricardo Marlière - EOS Brazil [@rbmarliere]: let us know when its up
  2448. 04.06.2018 19:31:13, Chitty 🅑 - EOS Argentina [@JChitty]: +1
  2449. .....04.06.2018 19:31:18, Timothy Lewis [@trustlayer]: >>unsupported service message type: messageActionChatAddUsers<<
  2450. .....04.06.2018 19:55:10, Timothy Lewis [@trustlayer]: >>invited Rafael LaVerde [@VamosRaf]<<
  2451. 04.06.2018 20:12:19, mini - EOS Argentina [@moonxor]: it seems that the idea of coordinating the communication didnt work.
  2452. 04.06.2018 20:14:50, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I think I need a status update of where everthing is at
  2453. 04.06.2018 20:15:10, mini - EOS Argentina [@moonxor]: to be honest me too
  2454. 04.06.2018 20:20:25, An Byung Chan - EOSYS [@Anbyungchan]: +1
  2455. 04.06.2018 20:25:50, Joshua Qiu @EOSeco [@Joshuaqiu]: it seem we can find guys in GB to talk?
  2456. 04.06.2018 20:26:18, Timothy Lewis [@trustlayer]: EOS Core channel
  2457. .....04.06.2018 21:19:35, J Y [@y30nj]: >>invited Wayne Fu [@waynefu]<<
  2458. .....04.06.2018 21:49:35, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: >>invited Luke Stokes [@lukestokes]<<
  2459. .....04.06.2018 21:51:03, David Moss [@DavidMoss]: >>invited Christo Boshoff [@ChristoBoshoff]<<
  2460. 04.06.2018 22:24:39, nahu [@naueh]: I think one of of the core premises from the p2p movement is to leverage cooperation against competition. Building tools to reduce the risk of trusting eack other brings an oportunity to disrupt the feartul<==>aggresive-competition feedback loop. A ridiculously destructive social mindset I'd say
  2461. 04.06.2018 22:28:18, nahu [@naueh]: I guess that this fear blinds the ability to identify common objectives, which are evidently more valuable and sustainable than all the individual ones together.
  2462. Matter of fact is that this is only obtainable through a convergence of agreements and efforts.
  2463. Isn't that what consensus is about after all?
  2464. 04.06.2018 22:29:18, mini - EOS Argentina [@moonxor]: +1000
  2465. 04.06.2018 22:29:43, Timothy Lewis [@trustlayer]: Absolutely.
  2466. 04.06.2018 22:31:01, nahu [@naueh]: Demoracy as we know it, seems to me just as an attempt that has not been able to scale properly to fulfill those requirements, so far
  2467. 04.06.2018 22:33:26, nahu [@naueh]: Random thoughts, sorry for the OT. I think my point is that we will have to commonly face some fucking big responsabilities sooner or later. I find what's going on here an unseen oportunity to try
  2468. 04.06.2018 22:35:48, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Let’s keep this channel for BP teams to report progress on Validation.
  2469. 04.06.2018 22:40:42, nahu [@naueh]: of course. Borught this thoughts here because I find this channel the most collaborative one right now, and want to highlight the value I find on that
  2470. 04.06.2018 22:57:17, Ricardo Marlière - EOS Brazil [@rbmarliere]: % cleos get code eosio
  2471.  
  2472. shouldn't this output match with $(sha256sum /path/to/eos/build/contracts/eosio.system/eosio.system.wasm)?
  2473.  
  2474. @abourget what am I missing? this is true for eosio.msig but not for eosio.token or eosio... currently checking on chain_id 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5 with launch-rc branch contracts...
  2475. 04.06.2018 23:27:19, Alexandre Bourget - EOS Canada [@abourget]: [[Webpage]]that's the reference contract used:
  2476. - name: eosio.system.wasm
  2477. ref: /ipfs/QmVTwpwBSWEWYT1dWHhgueZf2MmjsTuMRQXygvh7VxJHUE
  2478. comment: "~v1.0.1 from github.com/EOS-Mainnet/eos"
  2479. From the EOS-Mainnet/eos repo, just after the B1 tag v1.0.1
  2480. 04.06.2018 23:29:54, Alexandre Bourget - EOS Canada [@abourget]: Can you run a WAST comparison ? That would be helpful. Please report back soon.
  2481. 04.06.2018 23:34:50, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: [[Webpage]]If anyone want to test voting, staking, unstaking, refund, etc. You can use our little tool to do that, would love to help. https://github.com/eoslaomao/eos-cluster-generator
  2482. 04.06.2018 23:34:53, Ricardo Marlière - EOS Brazil [@rbmarliere]: hold on I'll rebuild v1.0.1
  2483. 04.06.2018 23:36:28, Alexandre Bourget - EOS Canada [@abourget]: Contracts have not changed since v1.0.0
  2484. 04.06.2018 23:36:31, Jacky - JEDA [@newbdez33]: I will try it later. Thanks!
  2485. 04.06.2018 23:37:49, mini - EOS Argentina [@moonxor]: awesome!
  2486. .....04.06.2018 23:38:59, Emily Bush - shEOS [@emmybush]: >>unsupported service message type: messageActionChatAddUsers<<
  2487. 04.06.2018 23:47:56, Alexandre Bourget - EOS Canada [@abourget]: Ok, I just checked multiple builds with clean environments. v1.0.0 from eosio/eos, v1.0.1 from eosio/eos and v1.0.1 from EOS-Mainnet/eos .. they all match the contract that is on-chain. If you have any concerns, please bring them forward.
  2488.  
  2489. I can also confirm that the builds from EOS Amsterdam have the same output. https://hub.docker.com/r/eosamsterdam/eos on the tag v1.0.1
  2490.  
  2491. Make sure you build with the EOS and not SYS, try with a clean build environment if needed. You'll get there :)
  2492. 04.06.2018 23:50:09, Patrick B - Aloha EOS: 👍
  2493. 04.06.2018 23:50:23, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: So, I'm checking the document "EOS Mainnet Validation Plan", and I do not see any progress on any task. I don't see anyone flagging "verified" any task. Are we at the same place we were 2 days ago?
  2494. 04.06.2018 23:51:06, mini - EOS Argentina [@moonxor]: no
  2495. 04.06.2018 23:51:54, Sharif Bouktila - EOS Dublin [@sharifbouktila]: That should now be used as a guide but each BP is responsible for their own testing to whatever scope and depth the feel necessary.
  2496. 04.06.2018 23:51:57, mini - EOS Argentina [@moonxor]: actually please read the laomao message :)
  2497. 04.06.2018 23:51:59, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: I'm worried that we start a call in ~8h and we start hearing again "we haven't reached a consensus of what to test", like we did 2 days ago, like we did 12 hours ago
  2498. 04.06.2018 23:52:22, Timothy Lewis [@trustlayer]: Quick question... What was the workaround for the RAM cost issue?
  2499. 04.06.2018 23:53:39, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: Which message?
  2500. 04.06.2018 23:53:53, mini - EOS Argentina [@moonxor]: this one
  2501. 04.06.2018 23:54:05, mini - EOS Argentina [@moonxor]: and the other one where they said they test unstacking :)
  2502. 04.06.2018 23:55:47, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: That is post is for a tool to help testing, but again, there is no checkmark in the validation document.
  2503. 04.06.2018 23:56:06, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: So we will be in a call tomorrow with no progress
  2504. 04.06.2018 23:56:09, mini - EOS Argentina [@moonxor]: you can test it if you want with that tool :)
  2505. 04.06.2018 23:56:19, mini - EOS Argentina [@moonxor]: i trust they test it
  2506. 04.06.2018 23:57:00, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: OK, so the plan is "as nobody reported any issues, we'll asume everything is OK" which is a perfect plan IMHO
  2507. 04.06.2018 23:57:11, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: is that the plan?
  2508. 04.06.2018 23:57:16, mini - EOS Argentina [@moonxor]: if you want to help, please help :)
  2509. 04.06.2018 23:57:43, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: I want to know if we will be stuck tomorrow as we were today
  2510. 04.06.2018 23:58:56, Timothy Lewis [@trustlayer]: +1
  2511. 04.06.2018 23:59:09, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We will be asking BP teams to confirm that have tested and are happy , if enough do we are good.
  2512.  
  2513. Decentralized QA.
  2514.  
  2515. Validation plan should be used as a guide. But feel free to test more or less.
  2516. 04.06.2018 23:59:34, mini - EOS Argentina [@moonxor]: +1 that was the idea all along
  2517. 05.06.2018 00:00:00, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Just took us a while to get there :)
  2518. 05.06.2018 00:00:44, David Moss [@DavidMoss]: Exactly
  2519. 05.06.2018 00:10:04, Ricardo Marlière - EOS Brazil [@rbmarliere]: I'll drop it. Of course different platforms would produce different binaries (tested on another distro just now), thanks for your time
  2520. 05.06.2018 00:11:02, Timothy Lewis [@trustlayer]: Quick question... What was the workaround for the RAM cost issue? @marcantoineross
  2521. 05.06.2018 00:11:41, Timothy Lewis [@trustlayer]: @sharifbouktila ?
  2522. 05.06.2018 00:12:00, Sharif Bouktila - EOS Dublin [@sharifbouktila]: ?
  2523. 05.06.2018 00:12:14, Timothy Lewis [@trustlayer]: The account generation issue
  2524. 05.06.2018 00:12:28, Timothy Lewis [@trustlayer]: with ever so slightly increasing ram costs.
  2525. 05.06.2018 00:13:29, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I think everyone was using Alex’s approach , create funds and burn any remaining.
  2526. 05.06.2018 00:14:08, Craig Murray - EOS BlockSmith [@craigmurray100]: the way they solved it is to over-fund eosio, then give out all the acconts in the snapshot, add up how much it cost, and then you know the total. Now do it again, funding eosio from total. Pretty sure this is how it was done
  2527. 05.06.2018 00:14:29, Timothy Lewis [@trustlayer]: Is that what was used in the genesis? Increased token supply to run and then burn?
  2528. 05.06.2018 00:14:33, mini - EOS Argentina [@moonxor]: are you talking about the snapshot? is not an issue if you use buy ram bytes,
  2529. 05.06.2018 00:17:06, Timothy Lewis [@trustlayer]: Could you explain this resolution?
  2530. 05.06.2018 00:17:19, Timothy Lewis [@trustlayer]: Did we have to increase the initial supply?
  2531. 05.06.2018 00:17:27, mini - EOS Argentina [@moonxor]: [[Webpage]]https://github.com/EOSIO/eos/blob/5d60cfbeff32576742d9a28d6278c13b524111cc/contracts/eosio.system/delegate_bandwidth.cpp#L88
  2532. 05.06.2018 00:17:43, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Yes the initial supply is over 1B
  2533. 05.06.2018 00:18:23, Timothy Lewis [@trustlayer]: Was this the solution used?
  2534. 05.06.2018 00:18:25, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: in the end, there are like only 2.034 EOS extra left to eosio account
  2535. 05.06.2018 00:18:52, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: the extra EOS is used to inject the snapshot, because you have to buy ram for new accounts.
  2536. 05.06.2018 00:19:09, Timothy Lewis [@trustlayer]: What was the initial token supply used?
  2537. 05.06.2018 00:19:34, Timothy Lewis [@trustlayer]: Anyone recall?
  2538. 05.06.2018 00:19:45, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: we dont have to recall
  2539. 05.06.2018 00:19:58, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: you can see that in the boot sequence file
  2540. 05.06.2018 00:20:39, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: https://ipfs.io/ipfs/QmXsZX3LVnisnDoaVYCK215fQorDcnjJpx5XDaBppzeERQ
  2541. 05.06.2018 00:21:14, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: [[Photo]]
  2542. 05.06.2018 00:21:26, Timothy Lewis [@trustlayer]: Ok just wanted to confirm.
  2543. 05.06.2018 00:21:35, Timothy Lewis [@trustlayer]: I have a problem with this that I would like to raise.
  2544. 05.06.2018 00:21:47, Timothy Lewis [@trustlayer]: There is an unexpected consequence.
  2545. 05.06.2018 00:22:09, Timothy Lewis [@trustlayer]: Increasing the initial supply increases BP rewards.
  2546. .....05.06.2018 00:22:16, Maja V [@mvparadigm]: >>invited Benjamin Vujinovic [@benjaminvu]<<
  2547. 05.06.2018 00:22:45, Timothy Lewis [@trustlayer]: Something to keep in mind.
  2548. 05.06.2018 00:22:59, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: by the end of boot, the supply is like 1 000 000 002 EOS
  2549. 05.06.2018 00:25:58, Timothy Lewis [@trustlayer]: taxation is theft? 😉 I can live with that.
  2550. 05.06.2018 00:34:40, mini - EOS Argentina [@moonxor]: [[Webpage]]yes you are right
  2551. https://github.com/EOSIO/eos/blob/master/contracts/eosio.system/producer_pay.cpp#L84
  2552. 05.06.2018 00:35:01, Timothy Lewis [@trustlayer]: #justsaying
  2553. 05.06.2018 01:10:57, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Regardless of how the next few hours play out. I believe everyone here only wants to see One EOS Mainnet
  2554.  
  2555. There is no winners and losers in this. Each team has contributed enormously to get us here.
  2556.  
  2557. This has got to be the largest Technology Project ever delivered. It has been a privilege to be apart of it.
  2558.  
  2559. It is a block producers duty to protect the interests of EOS token holders, and that duty is there before during and after launch.
  2560.  
  2561. I wrote in our BP announcement Post , being a block producer is akin to the Janitor in NASA helping put a man on the moon. Certainly feels that way now.
  2562.  
  2563. Lets not rush the final stages here. Take your time and lets get this right. and also lets ensure a level playing field for all teams, hopefully we will be working as partners for a long time to come.
  2564. 05.06.2018 01:52:20, Timothy Lewis [@trustlayer]: HERE HERE!
  2565. 05.06.2018 01:52:32, Timothy Lewis [@trustlayer]: Or HEAR HEAR!
  2566. 05.06.2018 01:52:41, Timothy Lewis [@trustlayer]: Whatever it is, I am proud of you all.
  2567. 05.06.2018 02:19:25, Timothy Lewis [@trustlayer]: Anyone else think we should decrease the time in between validation and check up calls?
  2568. 05.06.2018 02:19:47, Timothy Lewis [@trustlayer]: @marcantoineross @abourget @sharifbouktila ?
  2569. 05.06.2018 02:20:54, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Validation is 13:00 UTC , i know most teams have that in their diary.
  2570.  
  2571. What check up call ?
  2572. 05.06.2018 02:23:44, Timothy Lewis [@trustlayer]: I get that.
  2573. 05.06.2018 02:23:54, Timothy Lewis [@trustlayer]: It would be cool to increase that to twice a day.
  2574. 05.06.2018 02:24:09, Timothy Lewis [@trustlayer]: Just to come together a bit more often.
  2575. 05.06.2018 02:24:28, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Sure, what ever is necessary we will do it.
  2576. 05.06.2018 03:12:39, Crystal Rose | ⚡️SENSE | 💜shEOS [@crystalrose]: Let's call it Mainnet.one
  2577. 05.06.2018 03:24:28, Chitty 🅑 - EOS Argentina [@JChitty]: [[Webpage]]We found an issue that doesn't allow us to validate the eos.system , we have reported on GitHub: https://github.com/EOSIO/eos/issues/3824
  2578. 05.06.2018 03:26:28, David P - EOS42 [@GunnisonCap]: Agree with that, we should have 12hr check in calls after the 13:00 from now til mainnet launch and for the 24hrs immediately after.
  2579. 05.06.2018 03:27:17, David P - EOS42 [@GunnisonCap]: Who owns the domain name is the big question 😉
  2580. 05.06.2018 03:30:54, Crystal Rose | ⚡️SENSE | 💜shEOS [@crystalrose]: decentralize it. submitted .eos for gTLD / SLD consideration to ICANN just for kicks.
  2581. 05.06.2018 03:32:24, David P - EOS42 [@GunnisonCap]: Yeah I think it’s expensive so was thinking one of the first worker proposal funds should be that, but all the better if you work some magic now 😁
  2582. 05.06.2018 03:43:00, mini - EOS Argentina [@moonxor]: so if we want to validate a eosio.system, we cant do it automatically, we need to decode the wasm to wast and validate it manually.
  2583. 05.06.2018 03:50:54, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: maybe there’s something dynamic during building process?
  2584. 05.06.2018 03:51:19, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: not a C writer, forgive me if Im wrong
  2585. 05.06.2018 03:52:17, WinLin-EOSBIXIN [@hiwinlin]: [[Photo]]
  2586. 05.06.2018 03:53:18, WinLin-EOSBIXIN [@hiwinlin]: Hi all, sorry for late, I have finish the smart contract set & replace/upgrade test. It succeed and test pass
  2587. 05.06.2018 03:53:19, mini - EOS Argentina [@moonxor]: @zhaoyu i just read C++ i dont write it. I dont really know what is going on :( . but you can find the leak information in your eosio.system.wast file inside the build folder.
  2588. 05.06.2018 03:54:22, Timothy Lewis [@trustlayer]: 👏
  2589. 05.06.2018 03:56:03, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: +1
  2590. 05.06.2018 03:57:38, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: cool
  2591. 05.06.2018 04:04:29, Leonard Dorlöchter - EOS network by Advanced Blockchain AG [@EOSnetwork]: happy to support that. I researched the process in detail previously. It takes a while and is expensive so it probably has to be one of the first worker proposal funds like David says 🙂
  2592. .....05.06.2018 04:26:10, Jack - AcroEOS [@gjacklee]: >>invited 경수 민 [@Ryuk0]<<
  2593. 05.06.2018 05:31:34, Ville Sundell [@SolariusFI]: That would be cool 🙂
  2594. 05.06.2018 06:36:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: For this issue.
  2595.  
  2596. It looks like there is a fix suggested. If correct can this be applied to the chains currently?
  2597.  
  2598. Who in our community can check/ merge and test this ??
  2599.  
  2600. I don't believe we need to wait for Block.one and @daniellarimer to fix small issues. If our fix is correct I'm sure they would incorporate into their codebase also.
  2601.  
  2602. What does everyone else think ???
  2603. .....05.06.2018 06:37:29, Lucas @EOS Beijing [@LucasEosBeijing]: >>invited Allen@EOS Beijing [@fightinglion]<<
  2604. .....05.06.2018 06:40:03, Rafael LaVerde [@VamosRaf]: >>invited Jeff B [@jberwick]<<
  2605. 05.06.2018 06:40:38, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Seems pretty minor, its not even a fix its just an eosio_build change
  2606. 05.06.2018 06:44:43, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: You can do a pull request to the eos-Mainet repository. That one is managed by the community, not by B1.
  2607. 05.06.2018 06:46:14, mini - EOS Argentina [@moonxor]: You need to relaunch the chain
  2608. 05.06.2018 06:46:39, mini - EOS Argentina [@moonxor]: Or at least. A hardfork
  2609. 05.06.2018 06:47:16, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Hey mini btw ran firestarter against bios, got thi error while validating consitution
  2610. 05.06.2018 06:47:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: FAIL
  2611.  
  2612. ##########################################################
  2613. 'ascii' codec can't encode character u'\u2019' in position 723: ordinal not in range(128)
  2614. Traceback (most recent call last):
  2615. File "validator.py", line 27, in <module>
  2616. getattr(validator,'validate')(args)
  2617. File "/Users/nathan.rempel/firestarter/validator/vanilla_validator.py", line 606, in validate
  2618. if not validate_system_accounts(eos_snapshot): return
  2619. File "/Users/nathan.rempel/firestarter/validator/vanilla_validator.py", line 345, in validate_system_accounts
  2620. f.write(current_abi["ricardian_clauses"][0]["body"])
  2621. UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in position 723: ordinal not in range(128)
  2622. 05.06.2018 06:47:35, Alexandre Bourget - EOS Canada [@abourget]: The one in 579a is one agreed upon by many members of the community. It's not a blocker imo. And it can be upgraded.
  2623. 05.06.2018 06:47:59, Nathan Rempel | GenerEOS Sydney [@nsrempel]: is the hash issue when running "get code"
  2624. 05.06.2018 06:48:13, Nathan Rempel | GenerEOS Sydney [@nsrempel]: will return different results for different set contracts?
  2625. 05.06.2018 06:49:12, Alexandre Bourget - EOS Canada [@abourget]: The .wasm output is crippled, but the hash displayed on screen from get code is correct.
  2626. 05.06.2018 06:49:16, mini - EOS Argentina [@moonxor]: This Is because i think ' Is not únicode, need to check the parsing
  2627. 05.06.2018 06:49:51, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Agreed not blocker
  2628. 05.06.2018 06:49:58, mini - EOS Argentina [@moonxor]: Is correct with the versión you build in your system
  2629. 05.06.2018 07:01:11, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: [[Webpage]]We built a tool to validate unregistered eos holders and balances: https://github.com/EOSLaoMao/eos-unregistered-validator
  2630.  
  2631. by the way, the unregistered onchain data of 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5 is VALID. 🙂
  2632.  
  2633. pretty simple tool, feel free to use it.
  2634. 05.06.2018 07:04:54, WinLin-EOSBIXIN [@hiwinlin]: 👍👍👍👍👍👍
  2635. 05.06.2018 07:05:10, Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer [@tyeenoprom]: Awesome!
  2636. 05.06.2018 07:05:21, Roman CryptoLions [@romanskaskiw]: great service to the community!
  2637. 05.06.2018 07:08:01, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: All holders are created equal, even they are [unregistered], right?
  2638. 05.06.2018 07:18:45, Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer [@tyeenoprom]: Have we clarified how to handle the [unregistered] accounts?
  2639. 05.06.2018 07:27:38, Nathan Rempel | GenerEOS Sydney [@nsrempel]: unreg are those not even saved by ETH key conversion correct?
  2640. 05.06.2018 07:27:51, Nathan Rempel | GenerEOS Sydney [@nsrempel]: like 0.2% or whatever?
  2641. 05.06.2018 07:29:48, [email protected] [@crazybits]: unregistered fund would be sent to a EOS system account for the holder to claim later
  2642. 05.06.2018 07:29:54, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: yeah less than 20 thousand i think
  2643. 05.06.2018 07:30:18, Nathan Rempel | GenerEOS Sydney [@nsrempel]: what was the xplanation why they couldn't be saved? did those balances get sent into ETH smart contracts?
  2644. 05.06.2018 07:31:24, Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer [@tyeenoprom]: I know it will be sent to a EOS system account, in what way can the ETH holders claim their tokens?
  2645. 05.06.2018 08:03:20, Alexandre Bourget - EOS Canada [@abourget]: EVERYONE:
  2646.  
  2647. I propose, as we agreed yesterday, that at 1315 UTC today, the 579a chain starts accepting transactions.
  2648.  
  2649. It will allow for the next stage of tests..
  2650. 05.06.2018 08:04:25, Craig Murray - EOS BlockSmith [@craigmurray100]: 😅👍
  2651. 05.06.2018 08:05:10, deck - EOS New York [@deckw]: {{FWD: deck - EOS New York [@deckw], 05.06.2018 08:05:01}}
  2652. Not sure if anyone has done this yet but I ran the firestart validation tool against the EOS Core network. It looked good with only one failure because they add an extra account. I believe this is expected:
  2653.  
  2654. Validating EOS blockchain snapshot against "EOS Vanilla validator (v0.1)"
  2655. Loading EOS snapshot OK
  2656. Loading ETH snapshot OK
  2657. Load EOS genesis OK
  2658. Validating genesis OK
  2659. Verifying global params vs genesis OK
  2660. Verifying user account creation OK
  2661. Verifying user account stake OK
  2662. Verifying user account code OK
  2663. Verifying user account permission OK
  2664. Verifying privileged accounts OK
  2665. Verifying extra accounts FAIL
  2666. ** > Extra account found genesisblock
  2667. 05.06.2018 08:05:57, Jae Chung - HKEOS [@jaechung]: 👍
  2668. 05.06.2018 08:07:21, Alexandre Bourget - EOS Canada [@abourget]: Do we want to have eosio.unregd ? It's 3M EOS /cc @nsrempel
  2669. 05.06.2018 08:12:37, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I think we must
  2670. 05.06.2018 08:12:58, Nathan Rempel | GenerEOS Sydney [@nsrempel]: whether or not its ever recoverable, it should stay in circulation until we know what to do with it
  2671. 05.06.2018 08:13:38, Denis | EOS Nation [@DenisCarriere]: 👍👌
  2672. 05.06.2018 08:17:17, Nathan Rempel | GenerEOS Sydney [@nsrempel]: nathan.rempel$ cleos -u http://mainnet.genereos.io get currency balance eosio.token eosio.unregd
  2673. 3301220.3641 EOS
  2674.  
  2675. 👍
  2676. 05.06.2018 08:18:21, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: 👍
  2677. 05.06.2018 08:33:30, Joshua Qiu @EOSeco [@Joshuaqiu]: test or validation？
  2678. 05.06.2018 08:34:40, Alexandre Bourget - EOS Canada [@abourget]: [[Webpage]]Regarding: https://github.com/EOSIO/eos/issues/3824
  2679.  
  2680. It seems that some build paths sneaked into the .wasm output. All Docker builds I saw (ours, EOS Amsterdam, EOS BIXIN) probably use a default path, so gave the exact same output.
  2681.  
  2682. If you have built the eosio.system contract from a different path, comparison will fail. Easiest way to compare, is run the Docker build, which can more easily reproduce the environments.
  2683.  
  2684. This does not change any functionality in the contract, and we can clean-up later without risks.
  2685.  
  2686. If we reset the chain, I fear we're back on validation for a few days.
  2687.  
  2688. What do you think ?
  2689. 05.06.2018 08:37:35, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Can we discuss this at 13:00 UTC - 24 minutes from now. If no risk I don't see why it can't be in a later maintenance release.
  2690. 05.06.2018 08:37:49, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Agree, if theres a comfirmed standardized build that yeilds same result, carry on
  2691. 05.06.2018 08:38:10, Jose Toriello [@josetoriello]: +1
  2692. 05.06.2018 08:39:54, Craig Murray - EOS BlockSmith [@craigmurray100]: 👍
  2693. 05.06.2018 08:43:13, Daniel Larimer [@daniellarimer]: [[Photo]]
  2694. 05.06.2018 08:44:27, Craig Murray - EOS BlockSmith [@craigmurray100]: 😂
  2695. 05.06.2018 08:44:43, Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer [@tyeenoprom]: 😂
  2696. 05.06.2018 08:45:19, Jacky - JEDA [@newbdez33]: 🤣
  2697. 05.06.2018 08:45:33, Denis | EOS Nation [@DenisCarriere]: 👍 if no risk we move it on to maintenance release
  2698. 05.06.2018 08:45:48, Daniel Larimer [@daniellarimer]: Just merged a fix for inclusion of local build system paths
  2699. 05.06.2018 08:46:11, David Moss [@DavidMoss]: Thanks @daniellarimer
  2700. 05.06.2018 08:46:18, Daniel Larimer [@daniellarimer]: https://github.com/EOSIO/eos/pull/3834/files
  2701. 05.06.2018 08:46:32, Alexandre Bourget - EOS Canada [@abourget]: Does it impact any functionality of previously compiled contract ? Is it more cosmetic ?
  2702. 05.06.2018 08:46:40, Daniel Larimer [@daniellarimer]: more cosmetic
  2703. 05.06.2018 08:46:42, Alexandre Bourget - EOS Canada [@abourget]: Docker builds give a deterministic output, so can be easily compared.
  2704. 05.06.2018 08:46:47, Alexandre Bourget - EOS Canada [@abourget]: Ok, thanks.
  2705. 05.06.2018 08:50:33, Sharif Bouktila - EOS Dublin [@sharifbouktila]: @daniellarimer fancy coming on our Validation call in 10 mins ?
  2706. 05.06.2018 08:53:13, Ken (EOSphere) [@ken_eosphere]: 👍
  2707. 05.06.2018 08:53:14, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: What link?
  2708. 05.06.2018 08:54:37, James Sutherland - Cypherglass.com [@JamesSutherland]: Yes link me please Seymour.
  2709. 05.06.2018 08:54:39, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]https://zoom.us/j/692622137
  2710. 05.06.2018 08:55:13, James Sutherland - Cypherglass.com [@JamesSutherland]: Those EOS Dublin guys, always on the ball! I like it!
  2711. .....05.06.2018 09:32:38, lo chaiching [@lochaiching]: >>invited Yvonne (EOShenzhen) [@yvonnekama]<<
  2712. 05.06.2018 09:33:50, Jae Chung - HKEOS [@jaechung]: [[Photo]]
  2713. 05.06.2018 09:34:02, Jae Chung - HKEOS [@jaechung]: as requested in the Zoom call
  2714. 05.06.2018 09:34:49, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: the orange box is the "you are here" in the map?
  2715. 05.06.2018 09:37:39, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Is there yet a published protocol for coordinating and communicating tests, e.g. who is going to run which test, and what results they got? If not I’ll help create one; if there is I’ll help share it.
  2716. 05.06.2018 09:40:51, Michael Yeates [@michaelyeates]: all tests should be scripted and put in a collective github
  2717. 05.06.2018 09:41:10, Michael Yeates [@michaelyeates]: [[Webpage]]theres a skeleton test runner here https://github.com/michaeljyeates/ghostbustertests
  2718. 05.06.2018 09:41:34, Michael Yeates [@michaelyeates]: we will start adding tests today which will be runnable by anyone
  2719. 05.06.2018 09:42:56, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Good, I see the spreadsheet. I don’t see a protocol (list of idiot-proof steps to follow) to ID which test I will perform, register myself as the one testing, perform the test, save my test script into a repo, and log my results.
  2720. 05.06.2018 09:44:00, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: If there's any agreement that a protocol woudl be useful, I'll convene a small group to tackle this, in 90 min from now
  2721. 05.06.2018 09:47:33, Jose Toriello [@josetoriello]: 👍
  2722. 05.06.2018 09:47:47, Michael Yeates [@michaelyeates]: i think it would be useful to coordinate test writers so that we make sure we have full coverage
  2723. 05.06.2018 09:48:53, Craig Murray - EOS BlockSmith [@craigmurray100]: @DavidMoss Thank you for joining us this morning, and for speaking up. That was extremely helpful
  2724. 05.06.2018 09:49:04, Sam - EOS Dublin [@samnoble]: And to make sure we're all absoultely certain we're testing the same version of nodeos
  2725. 05.06.2018 09:49:38, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: same here..
  2726. 05.06.2018 09:50:23, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Can the "accelerated validation tool suite" be revised to use to use existing nodes rather than docker cluster (i assume yes) and drop the unstake test. Is it comprehensive enough that people can agree to run it individually against the cloned candidate net fullnodes
  2727. .....05.06.2018 09:50:41, Benjamin Wang | EOShenzhen [@iBenjaminWang]: >>invited Sheldon | EOShenzhen [@SheldonXP]<<
  2728. 05.06.2018 09:50:47, Nathan Rempel | GenerEOS Sydney [@nsrempel]: how many of the proposed acceptance tests will it cover?
  2729. 05.06.2018 09:50:53, Ville Sundell [@SolariusFI]: Thanks everyone for the call!
  2730. 05.06.2018 09:51:18, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: The public endpoints for each chain should be all in one place too
  2731. 05.06.2018 09:51:27, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: So people can run tests through all chains
  2732. 05.06.2018 09:52:08, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 👍
  2733. 05.06.2018 09:52:11, Jae Chung - HKEOS [@jaechung]: {{FWD: Michael Yeates [@michaelyeates], 05.06.2018 08:47:10}}
  2734. Public endpoints are now open, please use this genesis file{
  2735. "initial_timestamp": "2018-06-04T00:00:00.001",
  2736. "initial_key": "EOS7NjFmKkHsCTdT56RihFzhBVqdBhp9m2W6KpTKAFcVdvd18VKAE",
  2737. "initial_configuration": {
  2738. "max_block_net_usage": 1048576,
  2739. "target_block_net_usage_pct": 1000,
  2740. "max_transaction_net_usage": 524288,
  2741. "base_per_transaction_net_usage": 12,
  2742. "net_usage_leeway": 500,
  2743. "context_free_discount_net_usage_num": 20,
  2744. "context_free_discount_net_usage_den": 100,
  2745. "max_block_cpu_usage": 200000,
  2746. "target_block_cpu_usage_pct": 1000,
  2747. "max_transaction_cpu_usage": 150000,
  2748. "min_transaction_cpu_usage": 100,
  2749. "max_transaction_lifetime": 3600,
  2750. "deferred_trx_expiration_window": 600,
  2751. "max_transaction_delay": 3888000,
  2752. "max_inline_action_size": 4096,
  2753. "max_inline_action_depth": 4,
  2754. "max_authority_depth": 6
  2755. }
  2756. }
  2757. 05.06.2018 09:52:15, Jae Chung - HKEOS [@jaechung]: {{FWD: Michael Yeates [@michaelyeates], 05.06.2018 08:47:50}}
  2758. These are the endpoints
  2759.  
  2760. nodetest.eosio.africa:9886
  2761. nodetest0.eosio.africa:9895
  2762. nodetest1.eosio.africa:9895
  2763.  
  2764. 40.85.223.230:9875
  2765. 40.85.223.230:9874
  2766. 40.85.223.230:9873
  2767. 05.06.2018 09:52:25, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]Next Validation Call - 18:00 UTC 5th June 2018
  2768.  
  2769. Zoom Link - https://zoom.us/j/911102470
  2770.  
  2771. Sheet is here: https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=0
  2772. .....05.06.2018 09:52:29, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>unsupported service message type: messageActionPinMessage<<
  2773. 05.06.2018 09:52:39, Jae Chung - HKEOS [@jaechung]: Here is the genesis and endpoints for the chain open for public validation
  2774. 05.06.2018 09:53:13, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Lets be explicit about which chain is which when sharing these? unless we're testing how the fork functionality works?
  2775. 05.06.2018 09:53:16, Ross (EOSphere) [@rossco99]: Is this an accelerated chain for testing running contracts etc.?
  2776. 05.06.2018 09:53:21, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i guess genesis will keep them seperate
  2777. 05.06.2018 09:53:56, Craig Murray - EOS BlockSmith [@craigmurray100]: p2p-peer-address = peer.eosn.io:9876
  2778. p2p-peer-address = 91.121.177.21:9876
  2779. p2p-peer-address = node1.eosgreen.io:19876
  2780. p2p-peer-address = boot.eostitan.com:9876
  2781. p2p-peer-address = mainnet.eoseco.com:10010
  2782. p2p-peer-address = m.jeda.one:3322
  2783. p2p-peer-address = p2p-1.eosnetwork.io:9876
  2784. p2p-peer-address = 23.22.71.127:9876
  2785. p2p-peer-address = abp-node.eoscalgary.io:5222
  2786. p2p-peer-address = eosbp.eosvillage.io:8181
  2787. p2p-peer-address = p2p-seoul.mainnet.eosnodeone.io:9976
  2788. p2p-peer-address = 185.159.128.146:9876
  2789. p2p-peer-address = 54.95.202.14:9876
  2790. p2p-peer-address = 35.234.53.243:9876
  2791. p2p-peer-address = eos.nodepacific.com:443
  2792. p2p-peer-address = fullnode.eoslaomao.com:443
  2793. p2p-peer-address = nl.eu-west.eosamsterdam.net:9867
  2794. p2p-peer-address = node2.blockeos.io:9987
  2795. p2p-peer-address = 18.188.38.75:9876
  2796. p2p-peer-address = 18.188.4.97:9876
  2797. p2p-peer-address = mainnet-prod.eossv.org:443
  2798. p2p-peer-address = 52.9.143.150:9876
  2799. p2p-peer-address = p2p.genereos.io:9876
  2800. p2p-peer-address = rvk1.sheos.org:1876
  2801. p2p-peer-address = 18.234.6.119:80
  2802. p2p-peer-address = 13.71.188.181
  2803. p2p-peer-address = 130.211.59.178:9876
  2804. p2p-peer-address = node1.eosphere.io:9876
  2805. p2p-peer-address = node2.eosphere.io:9876
  2806. p2p-peer-address = mainnet.eoseco.com:10010
  2807. p2p-peer-address = bp.superone.io:443
  2808. p2p-peer-address = 52.79.113.58:9876
  2809. p2p-peer-address = 167.114.173.19:9996
  2810. p2p-peer-address = peer.eosio.sg:9876
  2811. p2p-peer-address = new.eoshenzhen.io:10010
  2812. p2p-peer-address = p2p.meet.one:9876
  2813. p2p-peer-address = peer1.eosthu.com
  2814. p2p-peer-address = 40.67.252.236:9999
  2815. p2p-peer-address = 35.197.190.234:19878
  2816. p2p-peer-address = eosapi.blockmatrix.network:13546
  2817. p2p-peer-address = publicnode.cypherglass.com:9876
  2818.  
  2819. This is a peer list for *9ea5 chain_id, the one Canada spun up 48 hours ago
  2820. 05.06.2018 09:54:05, Jae Chung - HKEOS [@jaechung]: yes genesis will keep them separate. It doesn't matter which chain you're testing really they are all equal candidates right?
  2821. 05.06.2018 09:54:44, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: @abourget have you cloned this chain already to let transactions run through?
  2822. 05.06.2018 09:54:49, Craig Murray - EOS BlockSmith [@craigmurray100]: if they have different genesis you should test both, no?
  2823. 05.06.2018 09:54:52, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: or will transactions only run through on EOS Core
  2824. 05.06.2018 09:55:02, Nathan Rempel | GenerEOS Sydney [@nsrempel]: correct, but i think people would rather know they aren't peered with chain a and running api tests on chain b? or that doesn't matter either?
  2825. 05.06.2018 09:55:33, Jae Chung - HKEOS [@jaechung]: that's what I'm saying. It doesn't matter which chain your testing, we don't need to give them names. Just take the genesis and endpoints and test these candidates and let's get through it
  2826. 05.06.2018 09:55:37, Craig Murray - EOS BlockSmith [@craigmurray100]: yes people should know who they are peered to, and who they are testing, 100%
  2827. 05.06.2018 09:56:01, Craig Murray - EOS BlockSmith [@craigmurray100]: yeah, so *0ea5 is one candidate. I gave a peer list for that
  2828. 05.06.2018 09:56:05, Sam - EOS Dublin [@samnoble]: Can I propose we create a tab for each of the two candidate nets in the spreadsheet. Including the genesis and a list of peers? @sharifbouktila can you update the pinned message to include a link to the spreadsheet again please.
  2829. 05.06.2018 09:56:07, Jae Chung - HKEOS [@jaechung]: yep
  2830. 05.06.2018 09:56:15, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: BIOS Chain ID: 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5
  2831.  
  2832. EOS Core Chain ID: 0d6c11e66db1ea0668d630330aaee689aa6aa156a27d39419b64b5ad81c0a760
  2833. 05.06.2018 09:56:28, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 👍
  2834. 05.06.2018 09:56:56, James Sutherland - Cypherglass.com [@JamesSutherland]: Could you post the genesis for this?
  2835. 05.06.2018 09:57:15, Sam - EOS Dublin [@samnoble]: @craigmurray100 and add it to the spreadsheet please
  2836. 05.06.2018 09:57:20, Sam - EOS Dublin [@samnoble]: @jaechung can you do the same for EOS CORE?
  2837. 05.06.2018 09:57:47, Jae Chung - HKEOS [@jaechung]: sure, could you link us the spreadsheet again?
  2838. 05.06.2018 09:58:09, Sharif Bouktila - EOS Dublin [@sharifbouktila]: spreadsheet pinned also
  2839. 05.06.2018 09:58:11, Sam - EOS Dublin [@samnoble]: [[Webpage]]https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=0
  2840. 05.06.2018 09:58:16, Sam - EOS Dublin [@samnoble]: Thanks @sharifbouktila
  2841. 05.06.2018 09:58:21, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I like Bios and Core, can get really pedantic and say CandidateNetB(ios) and CandidateNetC(ore)
  2842. 05.06.2018 09:58:44, Sharif Bouktila - EOS Dublin [@sharifbouktila]: B Chain / C Chain
  2843. 05.06.2018 09:58:49, Nathan Rempel | GenerEOS Sydney [@nsrempel]: ^^
  2844. 05.06.2018 09:58:49, Sam - EOS Dublin [@samnoble]: +1
  2845. 05.06.2018 09:59:19, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I like this differentiator
  2846. 05.06.2018 09:59:21, Sam - EOS Dublin [@samnoble]: We could go all out and use UUIDs 😉
  2847. 05.06.2018 10:00:03, Tim Weston - GenerEOS (BP Sydney) [@timweston]: I agree that ssteps like this need to be added to the spreadsheet so it can be quantified
  2848. 05.06.2018 10:01:15, Sam - EOS Dublin [@samnoble]: And are we all in agreement that we're running nodeos version 1603685708?
  2849.  
  2850. nodeos --version
  2851. 1603685708
  2852. 05.06.2018 10:01:32, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: +1
  2853. 05.06.2018 10:01:33, Tim Weston - GenerEOS (BP Sydney) [@timweston]: We dont want to have the testing being lost along the way otherwise we will go around in cirlces
  2854. 05.06.2018 10:01:37, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Running 1603685708
  2855. 05.06.2018 10:01:43, James Sutherland - Cypherglass.com [@JamesSutherland]: We should add that to the spreadsheet, nodeOS version
  2856. 05.06.2018 10:01:54, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: care to help craft the testing protocol?
  2857. 05.06.2018 10:01:56, James Sutherland - Cypherglass.com [@JamesSutherland]: For each chain
  2858. 05.06.2018 10:02:02, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Who else has the passion?
  2859. 05.06.2018 10:02:27, Nathan Rempel | GenerEOS Sydney [@nsrempel]: We also agreed then both Chain meshes will stay active? A rep from each will clone and pause/shutdown the chain in a state that can be restarted, remeshed, resynced? Should that backup be loaded into repo?
  2860. 05.06.2018 10:02:52, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i.e. the active chain meshes will go "beta" and start transaction testing, then get reverted
  2861. 05.06.2018 10:02:59, Tim Weston - GenerEOS (BP Sydney) [@timweston]: Can help for a bit but its getting late over in Australia 😳
  2862. 05.06.2018 10:03:10, Sam - EOS Dublin [@samnoble]: I've added a 'nodeos' sheet with the current version in. We can update that if we need to switch to a new version
  2863. 05.06.2018 10:04:55, Nathan Rempel | GenerEOS Sydney [@nsrempel]: which git tag/version is needed for 1603685708
  2864. 05.06.2018 10:06:17, deck - EOS New York [@deckw]: @sharifbouktila Can I request that 1 rep from each team is present. Having multiples can exclude other teams if we only have 100 slots
  2865. 05.06.2018 10:07:32, Jose Toriello [@josetoriello]: I can help coordinate
  2866. 05.06.2018 10:08:46, Joshua Qiu @EOSeco [@Joshuaqiu]: snapshot you use has md5 e9e3dd52360efb13e6ba0fd0070dcefb?
  2867. 05.06.2018 10:09:10, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Ive added API lists, if anyone wants to test running traffic against other node http apis
  2868. 05.06.2018 10:09:33, Nathan Rempel | GenerEOS Sydney [@nsrempel]: or if we share with non BP groups to run tests
  2869. 05.06.2018 10:10:14, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I dont have a list of these, so please self populate if you want to share
  2870. 05.06.2018 10:10:15, Ren Kaidi - EOSWTZ [@FoxMr]: which git tag/version is needed for 1603685708 ？
  2871. 05.06.2018 10:10:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: +1
  2872. 05.06.2018 10:10:27, James Sutherland - Cypherglass.com [@JamesSutherland]: +1
  2873. 05.06.2018 10:13:06, James Sutherland - Cypherglass.com [@JamesSutherland]: I tried building launch-rc and it wans't that version
  2874. 05.06.2018 10:13:46, Sam - EOS Dublin [@samnoble]: [[Webpage]]https://github.com/eosdublin/nodeos-template/tree/eos-mainnet/Ubuntu_16_04_LTS/launch-rc-5f964d4
  2875. 05.06.2018 10:14:05, Sam - EOS Dublin [@samnoble]: Commit 5f964d4cef7efaa7b76221c33616810afa8332e8 from the EOS Mainnet repo gives nodeos -v = 1603685708
  2876. 05.06.2018 10:14:26, deck - EOS New York [@deckw]: I think we should look to use launch-1.0.1
  2877. 05.06.2018 10:17:40, James Sutherland - Cypherglass.com [@JamesSutherland]: Confirmed commit 5f964d4cef7efaa7b76221c33616810afa8332e8 = 1603685708
  2878. 05.06.2018 10:17:50, Alexandre Bourget - EOS Canada [@abourget]: lol :)
  2879. 05.06.2018 10:17:58, Alexandre Bourget - EOS Canada [@abourget]: you switch to Dvorak mid-line ? :)
  2880. 05.06.2018 10:18:10, James Sutherland - Cypherglass.com [@JamesSutherland]: LMAO! Almost
  2881. 05.06.2018 10:20:10, Sam - EOS Dublin [@samnoble]: [[Webpage]]Ok, here's the diff https://github.com/EOS-Mainnet/eos/compare/launch-1.0.1...EOS-Mainnet:launch-rc
  2882.  
  2883. Does anyone object to upgrading to the launch-1.0.1 tag? https://github.com/EOS-Mainnet/eos/tree/launch-1.0.1
  2884. .....05.06.2018 10:22:53, Igor Lins e Silva - EOS Rio [@igorls]: >>invited Domi - EOS Rio [@domiscd]<<
  2885. 05.06.2018 10:40:12, WinLin-EOSBIXIN [@hiwinlin]: @jaechung please tell what accounts has been created in the net?
  2886. 05.06.2018 10:40:33, WinLin-EOSBIXIN [@hiwinlin]: I default with accounts:
  2887. ['eosio','eosio.msig','eosio.token','eosio.burned','eosio.names',
  2888. 'eosio.saving','eosio.bpay','eosio.vpay','eosio.disco',
  2889. 'eosio.ramfee','eosio.ram','eosio.unregd','eosio.stake']
  2890. 05.06.2018 10:40:35, Jae Chung - HKEOS [@jaechung]: one account: genesisblock
  2891. 05.06.2018 10:40:52, WinLin-EOSBIXIN [@hiwinlin]: does that lose someone ?
  2892. 05.06.2018 10:40:52, Jae Chung - HKEOS [@jaechung]: no eosio.unregd
  2893. 05.06.2018 10:41:17, Jae Chung - HKEOS [@jaechung]: no eosio.disco
  2894. 05.06.2018 10:41:26, WinLin-EOSBIXIN [@hiwinlin]: it's ok, the redundant account will make no harm
  2895. 05.06.2018 10:41:44, Jae Chung - HKEOS [@jaechung]: okay
  2896. 05.06.2018 10:41:51, WinLin-EOSBIXIN [@hiwinlin]: what is the use of genesisblock account ?
  2897. 05.06.2018 10:42:02, Jae Chung - HKEOS [@jaechung]: the one ABP
  2898. 05.06.2018 10:42:11, Jae Chung - HKEOS [@jaechung]: eosio —> genesisblock produces
  2899. 05.06.2018 10:42:16, WinLin-EOSBIXIN [@hiwinlin]: ok
  2900. 05.06.2018 10:42:58, WinLin-EOSBIXIN [@hiwinlin]: I will adjust my validation tool to support eos-bios and ghostbuster both
  2901. 05.06.2018 10:43:20, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: is there a detailed boot sequence? @jaechung
  2902. 05.06.2018 10:43:37, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: would like to run some validation test
  2903. 05.06.2018 10:45:03, Joshua Qiu @EOSeco [@Joshuaqiu]: you dont do any thing with snapshot_unregistered.csv?
  2904. 05.06.2018 10:45:09, WinLin-EOSBIXIN [@hiwinlin]: [[Webpage]]@jaechung I will use snapshot file: https://github.com/eosauthority/genesis/blob/master/snapshot-files/final/2/snapshot.csv
  2905. 05.06.2018 10:49:09, Joshua Qiu @EOSeco [@Joshuaqiu]: snapshot is all right ,pass my simple validation , but just let's unreg balance gone?
  2906. 05.06.2018 10:49:30, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: unreg is not deployed yet I believe
  2907. 05.06.2018 10:49:44, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: @michaelyeates
  2908. 05.06.2018 10:50:25, Jae Chung - HKEOS [@jaechung]: [[Webpage]]https://github.com/CryptoLions/EOS-Boot-Steps-dawn4
  2909. A variation of this, we changed a lot of stuff and ran bash scripts
  2910. 05.06.2018 10:50:40, Jae Chung - HKEOS [@jaechung]: @igorls knows more about that
  2911. 05.06.2018 10:51:04, Jae Chung - HKEOS [@jaechung]: sure thanks
  2912. 05.06.2018 10:51:09, Charles H - EOS 42 [@ankh2054]: @Joshuaqiu @syed_jafri contract will be implemented after community approval.
  2913. 05.06.2018 10:51:30, Michael Yeates [@michaelyeates]: we are waiting for community discussions on this contract but dont see a reason why we couldnt load the contract and populate it
  2914. 05.06.2018 10:52:17, Joshua Qiu @EOSeco [@Joshuaqiu]: which account hold these 3M EOS?
  2915. 05.06.2018 10:52:35, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: p2p-peer-address = node.eosmeso.io:9876 missing in that list :)
  2916. 05.06.2018 10:53:09, Michael Yeates [@michaelyeates]: who has some software acceptance testing scripts?
  2917. 05.06.2018 10:54:08, Igor Lins e Silva - EOS Rio [@igorls]: eosio still has them, they can be then transfered after approval using multisig
  2918. 05.06.2018 10:54:15, Marc-Antoine Ross - EOS Canada [@marcantoineross]: @zhaoyu does
  2919. 05.06.2018 10:55:04, Michael Yeates [@michaelyeates]: github link?
  2920. 05.06.2018 10:55:06, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: [[Webpage]]https://github.com/eoslaomao/eos-cluster-generator
  2921. 05.06.2018 10:55:56, Joshua Qiu @EOSeco [@Joshuaqiu]: eosio will not resign?and pulish private key?
  2922. 05.06.2018 10:56:08, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: it helps to setup a multp-bp local testnet quickly, and generate a bunch of scripts to test voting/staking/unstaking/ etc
  2923. 05.06.2018 10:56:34, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: once it’s booted up, kinda up to you to apply any test cases
  2924. 05.06.2018 10:58:01, Michael Yeates [@michaelyeates]: great, can we take the produced scripts to run against an existing network?
  2925. 05.06.2018 11:01:46, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: if you run your node with docker, it’s would be just change a few lines of code
  2926. 05.06.2018 11:07:36, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Super. Testing protocol breakout group will convene in 23 minutes, at 1130 AM EST / 1530 UTC
  2927. 05.06.2018 11:08:09, Michael Yeates [@michaelyeates]: do you have a link to the code?
  2928. 05.06.2018 11:09:32, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: do you guys have any thoughts about the cases that, EOS holders that missed the registration, also have no outgoing transcation from their ETH wallet, so the fallback mechanism couldnt cover that, either.
  2929. 05.06.2018 11:09:45, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: endup with no trace in the final snapshot
  2930. 05.06.2018 11:10:22, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: I had heard that all 1 billion tokens were accounted for, which implies that your concern is misplaced.
  2931. 05.06.2018 11:10:36, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Best to bring that up in the Snapshot group. Or ask Sandwich directly.
  2932. 05.06.2018 11:11:17, David Moss [@DavidMoss]: All but .1337 of one EOS token has been accounted for...
  2933. 05.06.2018 11:11:28, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Join here
  2934. https://t.me/joinchat/GgxZkRD5IzcLY8xNlu8ksg
  2935. 05.06.2018 11:11:38, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Need to store their ETH public key as a memo for easier claiming later imo
  2936. 05.06.2018 11:12:17, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: He means the content in the unregd account
  2937. 05.06.2018 11:12:26, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: I stand corrected, 999,999,999.8663 tokens are accounted for, and 0.1337 of a token is unaccounted for.
  2938. 05.06.2018 11:12:54, Roman CryptoLions [@romanskaskiw]: 1337 😊
  2939. 05.06.2018 11:14:33, Roshan - EOS Authority [@telepound]: [[Webpage]]Yes unregd account holds holds 0.3% or 3,301,220.3641 EOS is on a smart contract and not in the user account.
  2940.  
  2941. https://eosauthority.com/genesis
  2942. 05.06.2018 11:15:10, Michael Yeates [@michaelyeates]: do we have an agreement on where the ram fee should come from?
  2943. 05.06.2018 11:15:59, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Issue a higher initial supply
  2944. 05.06.2018 11:16:41, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: that’s what eos-bios do, with like 2.124 EOS extra token left to eosio acccount
  2945. 05.06.2018 11:16:53, Michael Yeates [@michaelyeates]: that will affect the pay to producers wouldnt it?
  2946. 05.06.2018 11:17:04, Michael Yeates [@michaelyeates]: ie producers would be paid more
  2947. 05.06.2018 11:17:43, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: By the end of boot, there would be a supply of 1 000 000 002 EOS, very close to 1 billion
  2948. 05.06.2018 11:17:53, Michael Yeates [@michaelyeates]: have we checked that?
  2949. 05.06.2018 11:17:59, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Yes, in BIOS
  2950. 05.06.2018 11:18:01, Craig Murray - EOS BlockSmith [@craigmurray100]: yes
  2951. 05.06.2018 11:18:03, Michael Yeates [@michaelyeates]: the supply was 1bn when i checked
  2952. 05.06.2018 11:18:04, Craig Murray - EOS BlockSmith [@craigmurray100]: with multiple tools
  2953. 05.06.2018 11:19:54, Denis | EOS Nation [@DenisCarriere]: How can someone fully validate/test the boot sequence if changes are still being made to the boot sequence? This type of information should be public, this is the reason why I would not trust any chain that is not being launched with eos-bios
  2954.  
  2955. What type of changes are still being added?
  2956. 05.06.2018 11:20:31, Michael Yeates [@michaelyeates]: we agreed that state was the important thing to validate
  2957. 05.06.2018 11:21:28, Craig Murray - EOS BlockSmith [@craigmurray100]: hrm, actually
  2958. 05.06.2018 11:21:36, Craig Murray - EOS BlockSmith [@craigmurray100]: ./cleos.sh get currency stats eosio.token "EOS"
  2959. {
  2960. "EOS": {
  2961. "supply": "1000011821.0000 EOS",
  2962. "max_supply": "10000000000.0000 EOS",
  2963. "issuer": "eosio"
  2964. }
  2965. }
  2966. 05.06.2018 11:22:51, Michael Yeates [@michaelyeates]: thats a bit more than 2 eos
  2967. 05.06.2018 11:23:08, Michael Yeates [@michaelyeates]: will lead to excessive inflation
  2968. 05.06.2018 11:24:48, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: maybe there should be an action log generated after launch in this way. bios-boot does a great job doing this. after all, it’s just a bunch of data, but we need to be verifying that really easily.
  2969. 05.06.2018 11:24:51, Denis | EOS Nation [@DenisCarriere]: Both state and boot sequence is important, why would hidding the boot sequence benefit anyone?
  2970. 05.06.2018 11:25:18, Michael Yeates [@michaelyeates]: nobody is hiding
  2971. 05.06.2018 11:25:26, Michael Yeates [@michaelyeates]: read the actions from the chain
  2972. 05.06.2018 11:25:38, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: after all accounts created, it will have 2 extra EOS left, which is not a big deal I think?
  2973. 05.06.2018 11:25:59, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Is this on 579a649aae8f660aa1abbab262437596d1f388f709b0b94a9fd6bba479889ea5?
  2974. 05.06.2018 11:26:02, Michael Yeates [@michaelyeates]: we are worried about total supply affecting block producer pay
  2975. 05.06.2018 11:26:13, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: lets test that
  2976. 05.06.2018 11:26:22, Michael Yeates [@michaelyeates]: people may think we added it so that we would benefit
  2977. 05.06.2018 11:27:03, Nathan Rempel | GenerEOS Sydney [@nsrempel]: What number do you get on latest? I'm running v1.0.1
  2978. 05.06.2018 11:27:12, Denis | EOS Nation [@DenisCarriere]: Only 2 EOS remains in eosio
  2979.  
  2980. $ cleos get currency balance eosio.token eosio EOS
  2981. 2.0312 EOS
  2982.  
  2983. Maybe @abourget can expand
  2984. 05.06.2018 11:27:30, Craig Murray - EOS BlockSmith [@craigmurray100]: yes.
  2985. 05.06.2018 11:27:52, Michael Yeates [@michaelyeates]: its the supply that is being questioned, not eosio balance
  2986. 05.06.2018 11:27:54, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Why is there 11000 EOS excess then, the accounts are already created
  2987. 05.06.2018 11:27:55, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: starting in 3 min
  2988. 05.06.2018 11:28:11, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: (Testing protocol workgroup)
  2989. 05.06.2018 11:29:46, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: you have to buy memery when u create new accounts, the extra 11000 EOS is used to pay that
  2990. 05.06.2018 11:29:49, Denis | EOS Nation [@DenisCarriere]: Is it from the creation of accounts?
  2991. 05.06.2018 11:30:20, Denis | EOS Nation [@DenisCarriere]: 👍Exactly what I thought, creating all those accounts cost RAM and eosio pays for that
  2992. 05.06.2018 11:31:17, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: so that users will have exact amount of EOS as they registered.
  2993. 05.06.2018 11:31:23, Craig Murray - EOS BlockSmith [@craigmurray100]: yes, it has all been accounted for over the last 48 hours
  2994. 05.06.2018 11:31:46, Denis | EOS Nation [@DenisCarriere]: eosio purchased 38.84 MB worth of RAM
  2995.  
  2996. $ cleos get account eosio
  2997. 05.06.2018 11:31:57, WinLin-EOSBIXIN [@hiwinlin]: [[Webpage]]@all I have finished the validation of Ghosterbuster testnet, you can download the lastest eos_onchain_validator.py from https://github.com/EOSBIXIN/eostoolkit/tree/master/eos_validator and to check by yourself
  2998. 05.06.2018 11:32:14, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: great
  2999. 05.06.2018 11:32:46, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: have you run that
  3000. 05.06.2018 11:32:47, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: ?
  3001. 05.06.2018 11:34:17, WinLin-EOSBIXIN [@hiwinlin]: he validation result is :
  3002. snapshot compare、account、balance validation is succeed.
  3003. But the codehash of eosio compare filed, please check @jaechung
  3004. 05.06.2018 11:34:29, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: I do think the proposal that we use bios-boot to inject all the actions, then hand it over to GB to run an ABP node producing blocks, is a smart one.
  3005. 05.06.2018 11:35:31, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: since bios-boot does a great job executing these actions and with proper logging of these actions. Also, they are plenty of tools to validate that, really fast.
  3006. 05.06.2018 11:35:51, WinLin-EOSBIXIN [@hiwinlin]: [[Photo]]
  3007. 05.06.2018 11:35:59, WinLin-EOSBIXIN [@hiwinlin]: [[Photo]]
  3008. 05.06.2018 11:36:26, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: multisig contract error？
  3009. 05.06.2018 11:36:36, WinLin-EOSBIXIN [@hiwinlin]: the eosio.system and eosio.bios contracts have some differences
  3010. 05.06.2018 11:37:00, Nathan Rempel | GenerEOS Sydney [@nsrempel]: is this related to the sha256 thing that was fixed/described?
  3011. 05.06.2018 11:37:05, WinLin-EOSBIXIN [@hiwinlin]: eosio.system and eosio.bios contracts has error
  3012. 05.06.2018 11:37:23, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: that only affects system contract, no?
  3013. 05.06.2018 11:37:54, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i think so
  3014. 05.06.2018 11:39:41, WinLin-EOSBIXIN [@hiwinlin]: [[Webpage]]that maybe just because of compile issue casue by https://github.com/EOSIO/eos/issues/3824
  3015. 05.06.2018 11:40:30, WinLin-EOSBIXIN [@hiwinlin]: but some prove should be supplied else I think there should be something wrong in the chain @jaechung
  3016. 05.06.2018 11:42:22, Ken (EOSphere) [@ken_eosphere]: [[Webpage]]Some snapshot injection validation results for registered accounts against the two chains - https://github.com/eosphere/candidate-chain-snapshot-verification thanks to @deckw tool eospy - .Total accounts: 163930.
  3017. 05.06.2018 11:42:24, Igor Lins e Silva - EOS Rio [@igorls]: multisig is working fine
  3018. 05.06.2018 11:42:30, Igor Lins e Silva - EOS Rio [@igorls]: @hiwinlin
  3019. 05.06.2018 11:43:23, WinLin-EOSBIXIN [@hiwinlin]: yes, multisig compare successfully
  3020. 05.06.2018 11:43:39, Igor Lins e Silva - EOS Rio [@igorls]: where is the error?
  3021. 05.06.2018 11:43:47, WinLin-EOSBIXIN [@hiwinlin]: but eosio.bios and eosio.system have difference
  3022. 05.06.2018 11:44:05, Igor Lins e Silva - EOS Rio [@igorls]: eosio.bios don't exist anymore
  3023. 05.06.2018 11:44:17, Igor Lins e Silva - EOS Rio [@igorls]: i don't understand the issue
  3024. 05.06.2018 11:44:32, WinLin-EOSBIXIN [@hiwinlin]: [[Photo]]
  3025. 05.06.2018 11:46:48, Igor Lins e Silva - EOS Rio [@igorls]: @hiwinlin are you checking state or history?
  3026. 05.06.2018 11:47:16, WinLin-EOSBIXIN [@hiwinlin]: I just comper the cosehash of eosio account ,you can get the info by :
  3027. cleos get code eosio
  3028. 05.06.2018 11:47:33, Igor Lins e Silva - EOS Rio [@igorls]: ba8f337948f958209ebf6aa7d3e4d699d909181a52a155dcac3ca4dd6afe0c52
  3029. 05.06.2018 11:48:21, WinLin-EOSBIXIN [@hiwinlin]: just supply some evidences that the eosio.system will not be modified and that will be ok
  3030. 05.06.2018 11:48:59, WinLin-EOSBIXIN [@hiwinlin]: [[Webpage]]hat maybe just because of compile issue casue by https://github.com/EOSIO/eos/issues/3824
  3031. 05.06.2018 11:49:24, Igor Lins e Silva - EOS Rio [@igorls]: [[Photo]]
  3032. 05.06.2018 11:49:26, Igor Lins e Silva - EOS Rio [@igorls]: please check this
  3033. 05.06.2018 11:49:39, Igor Lins e Silva - EOS Rio [@igorls]: it gives the exact same output here
  3034. 05.06.2018 11:51:17, WinLin-EOSBIXIN [@hiwinlin]: well I get :
  3035. $ sha256sum eosio.system.wasm
  3036. fdb35bf92a4e518739e90a1bc9ffed6d1aef94b31a279b52876d84025931af88 eosio.system.wasm
  3037. 05.06.2018 11:51:56, WinLin-EOSBIXIN [@hiwinlin]: [[Photo]]
  3038. 05.06.2018 11:52:08, WinLin-EOSBIXIN [@hiwinlin]: I build with docker and cmdline is :
  3039. 05.06.2018 11:52:22, WinLin-EOSBIXIN [@hiwinlin]: docker build -t winlin/eosmainnet:v1.0.1 --build-arg branch=v1.0.1 --build-arg symbol=EOS .
  3040. 05.06.2018 11:52:23, Igor Lins e Silva - EOS Rio [@igorls]: yes.. thats why your paths are different
  3041. 05.06.2018 11:53:13, Jae Chung - HKEOS [@jaechung]: you must use the same path @hiwinlin
  3042. 05.06.2018 11:53:34, Igor Lins e Silva - EOS Rio [@igorls]: also for the boost libs
  3043. 05.06.2018 11:54:13, Igor Lins e Silva - EOS Rio [@igorls]: [[Photo]]
  3044. 05.06.2018 11:54:20, WinLin-EOSBIXIN [@hiwinlin]: so, do you have write some artical about your boot sequances and describe what the desgin of your steps
  3045. that will make it more clear for the comminity I think
  3046. 05.06.2018 11:54:22, Igor Lins e Silva - EOS Rio [@igorls]: hardcoded paths on the wast file
  3047. 05.06.2018 11:54:57, WinLin-EOSBIXIN [@hiwinlin]: I hope to see the detail of your boot sequacnes, that will be more helpful
  3048. 05.06.2018 11:55:09, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: yeah, would love to have some sort of auto generated action log or something
  3049. 05.06.2018 11:55:57, WinLin-EOSBIXIN [@hiwinlin]: I need go to bad ,it is 00:00 AM, if you have any info please @ me tks
  3050. 05.06.2018 11:56:12, Craig Murray - EOS BlockSmith [@craigmurray100]: the boot sequence is not published for chain C? Seems like it should be
  3051. 05.06.2018 11:59:43, Igor Lins e Silva - EOS Rio [@igorls]: validation tools should not follow sequences, they should be able to validade state
  3052. 05.06.2018 12:01:15, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: good point
  3053. 05.06.2018 12:01:38, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: actually, you can fetch all the actions out from the chain
  3054. 05.06.2018 12:03:18, Craig Murray - EOS BlockSmith [@craigmurray100]: yes you can fetch the tx, and you can validate state, but it would also be nice to review the boot sequence that created them. Is there some reason to not publish this information?
  3055. 05.06.2018 12:04:35, Igor Lins e Silva - EOS Rio [@igorls]: all data is on chain
  3056. 05.06.2018 12:04:35, Jae Chung - HKEOS [@jaechung]: it hasn't been published yet, @igorls will do so now
  3057. 05.06.2018 12:04:56, Marc-Antoine Ross - EOS Canada [@marcantoineross]: 👍
  3058. 05.06.2018 12:05:19, Craig Murray - EOS BlockSmith [@craigmurray100]: thx! 👍
  3059. 05.06.2018 12:05:32, Marc-Antoine Ross - EOS Canada [@marcantoineross]: That will surely help reach full consensus on the content we want on chain, 1 more ✔️!
  3060. 05.06.2018 12:05:47, Jae Chung - HKEOS [@jaechung]: Along with the injector script too.
  3061. 05.06.2018 12:10:09, Igor Lins e Silva - EOS Rio [@igorls]:
  3062. run_cmd "set contract eosio "$CONTRACTS/eosio.bios" -p eosio";
  3063. run_cmd "create account eosio b1 EOS5cujNHGMYZZ2tgByyNEUaoPLFhZVmGXbZc9BLJeQkKZFqGYEiQ";
  3064. run_cmd "create account eosio eosio.msig $EOSIO_PUB"
  3065. run_cmd "create account eosio eosio.token $EOSIO_PUB"
  3066. run_cmd "create account eosio eosio.ram $EOSIO_PUB"
  3067. run_cmd "create account eosio eosio.ramfee $EOSIO_PUB"
  3068. run_cmd "create account eosio eosio.names $EOSIO_PUB"
  3069. run_cmd "create account eosio eosio.stake $EOSIO_PUB"
  3070. run_cmd "create account eosio eosio.saving $EOSIO_PUB"
  3071. run_cmd "create account eosio eosio.bpay $EOSIO_PUB"
  3072. run_cmd "create account eosio eosio.vpay $EOSIO_PUB"
  3073. run_cmd "push action eosio setpriv "'["eosio.msig",1]'" -p eosio"
  3074. run_cmd "set contract eosio.msig "$CONTRACTS/eosio.msig" -p eosio.msig"
  3075. run_cmd "set contract eosio.token "$CONTRACTS/eosio.token" -p eosio.token"
  3076. cleos push action eosio.token create '["eosio","10000000000.0000 EOS"]' -p eosio.token
  3077. cleos get currency stats eosio.token EOS
  3078. cleos push action eosio.token issue '["eosio", "1000000000.0000 EOS", "initial issuance"]' -p eosio
  3079. cleos get currency stats eosio.token EOS
  3080. run_cmd "set contract eosio "$CONTRACTS/eosio.system" -p eosio"
  3081. cleos push action eosio buyrambytes '["eosio","b1",8192]' -p eosio
  3082. cleos transfer eosio b1 "10.0000 EOS" "eosacknowledgments.io" -p eosio
  3083. cleos system delegatebw --transfer eosio b1 "49999995.0050 EOS" "49999995.0050 EOS"
  3084. ## inject tokens
  3085. ## revert eosio to system
  3086. ## resign eosio
  3087. 05.06.2018 12:10:51, Igor Lins e Silva - EOS Rio [@igorls]: here is some boot sequence
  3088. 05.06.2018 12:13:06, jem [@jemxpat]: For GB core paused net:
  3089.  
  3090. $ cleos get currency stats eosio.token "EOS"
  3091. {
  3092. "EOS": {
  3093. "supply": "1000000000.0000 EOS",
  3094. "max_supply": "10000000000.0000 EOS",
  3095. "issuer": "eosio"
  3096. }
  3097. }
  3098. 05.06.2018 12:17:37, Marc-Antoine Ross - EOS Canada [@marcantoineross]: can this be on github please?
  3099. 05.06.2018 12:18:17, Michael Yeates [@michaelyeates]: we are very busy validating the software at the moment
  3100. 05.06.2018 12:18:51, Marc-Antoine Ross - EOS Canada [@marcantoineross]: we'd like to help @michaelyeates. sharing code helps paralelize work
  3101. 05.06.2018 12:19:48, Igor Lins e Silva - EOS Rio [@igorls]: this draft? is totally irrelevant for validation
  3102. 05.06.2018 12:19:57, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: how did you manage to do this?
  3103. 05.06.2018 12:23:44, jem [@jemxpat]: As mentioned before, the fundamental cause of the difference in hash value is the inclusion of the absolute path of the build directory as part of the hashed data. Many have been using "/home/eos" as the base directory from which the code is built, including the boost libraries.
  3104.  
  3105. I guess that the base directory used in the Docker build is something different. Perhaps if /home/eos was used, it would give the same hash as we see.
  3106.  
  3107. While the hash and data in the files should be independent of the source code location, currently it is not. This is a bug, but overall just an annoyance when understood.
  3108. 05.06.2018 12:27:41, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Change path or have these changes: https://github.com/EOSIO/eos/pull/3834/files
  3109. 05.06.2018 12:30:07, Rohan - EOSauthority [@RohanWillAnswer]: [[Photo]]
  3110. 05.06.2018 12:30:34, Craig Murray - EOS BlockSmith [@craigmurray100]: should this be in github?
  3111. .....05.06.2018 12:43:07, Branden Espinoza [@espinbrand]: >>unsupported service message type: messageActionChatJoinedByLink<<
  3112. 05.06.2018 12:48:07, Ricardo Marlière - EOS Brazil [@rbmarliere]: 🙏
  3113. 05.06.2018 12:56:18, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: What time and link for the next meeting please?
  3114. 05.06.2018 12:59:18, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Report from the Test Protocol Workgroup:
  3115. 05.06.2018 12:59:18, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: {{FWD: Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox], 05.06.2018 12:46:35}}
  3116. Test Protocol group will be preparing a suggested protocol for two things:
  3117. 1. How to propose a UA test
  3118. 2. How to sign up for & run a UA test and report results
  3119. Work is being done by Branden Espinoza with assist from Sharif and Ross and at least 1 other
  3120. 05.06.2018 12:59:18, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: {{FWD: Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox], 05.06.2018 12:48:00}}
  3121. We have a draft statement of UA Testing Exit Criteria we'll be releasing.
  3122. Work on the draft is being done by Sharif and several others
  3123. 05.06.2018 12:59:19, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: {{FWD: Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox], 05.06.2018 12:49:28}}
  3124. The test protocol will be accompanied by a tool or set of tools to make it easier to keep the data accurate and complete
  3125. 05.06.2018 12:59:55, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Timeline is - in 60 minutes we will get a progress report from @espinbrand and an estimated time to completion
  3126. 05.06.2018 13:00:25, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: @sharifbouktila will share the draft Exit Criteria statement in I believe that same timeframe
  3127. 05.06.2018 13:54:26, Joshua Qiu @EOSeco [@Joshuaqiu]: do we still have meeting in 18 utc ?
  3128. 05.06.2018 13:54:31, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Proposed Validation Exit Criteria
  3129.  
  3130. 1. Completed Test Plan verified by multiple BP teams
  3131. 2. No new proposals of critical tests outstanding
  3132. 3. Confirmation from the EMLG that Validation is Complete (Go/No Go)
  3133. 4. Decision on which chain to enable for staking
  3134. 05.06.2018 13:54:52, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Yes in 6 minutes
  3135. 05.06.2018 13:55:03, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]https://zoom.us/j/911102470
  3136. 05.06.2018 13:55:56, mini - EOS Argentina [@moonxor]: Love this idea
  3137. 05.06.2018 13:56:30, mini - EOS Argentina [@moonxor]: +1
  3138. 05.06.2018 14:19:09, Joshua Qiu @EOSeco [@Joshuaqiu]: agree on issue
  3139. 05.06.2018 14:19:12, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Issue more tokens for accounts
  3140. 05.06.2018 14:19:17, Jae Chung - HKEOS [@jaechung]: Option 1: Take From Unregistered Accounts, Return them later on fallback registration
  3141. Option 2: Issue more tokens
  3142. 05.06.2018 14:19:59, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Option 3: Borrow from 'unregistered' balance, pay back loan from producer pay over first N days
  3143. 05.06.2018 14:20:13, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: What's the total number of tokens required, roughly?
  3144. 05.06.2018 14:20:14, James Sutherland - Cypherglass.com [@JamesSutherland]: Please say the amount
  3145. 05.06.2018 14:20:27, Nate D - Aloha EOS [@n8dee]: Yes, what is the amount? @abourget
  3146. 05.06.2018 14:21:58, Michael Yeates [@michaelyeates]: 11821
  3147. 05.06.2018 14:22:01, Domi - EOS Rio [@domiscd]: Option 1: Take From Unregistered Accounts, Return them later:
  3148.  
  3149. $ cleos get currency stats eosio.token "EOS"
  3150. {
  3151. "EOS": {
  3152. "supply": "1000000000.0000 EOS",
  3153. "max_supply": "10000000000.0000 EOS",
  3154. "issuer": "eosio"
  3155. }
  3156. }
  3157.  
  3158. Option 2: Issue more tokens:
  3159. {
  3160. "EOS": {
  3161. "supply": "1000011821.0000 EOS",
  3162. "max_supply": "10000000000.0000 EOS",
  3163. "issuer": "eosio"
  3164. }
  3165. }
  3166. 05.06.2018 14:22:02, Josh Kauffman - EOS Canada [@joshkauff]: {{FWD: WinLin-EOSBIXIN [@hiwinlin], 03.06.2018 05:52:37}}
  3167. and I run with issued '1,000,011,818.7401 EOS' but failed with error in record_unregsited:
  3168. assertion failure with message: overdrawn balance
  3169.  
  3170. so I change issue amount into "1000012000.0000 EOS" and run again, and successed, eosio balnace is 181.0276 EOS, so the final EOS issue should be :
  3171. 1000012000.0000 - 181.0276 = 1,000,011,818.9724
  3172. and the eosio.ram and eosio.ramfee may change 1-2 EOS,
  3173.  
  3174. so we can issue once and use 1,000,011,820.0000 EOS, and after BIOS, the balance of eosio is just 1-2 EOS left, which I think is ok
  3175. 05.06.2018 14:23:42, Josh Kauffman - EOS Canada [@joshkauff]: so if we round up and call that 12,000 extra tokens. that affects the supply by 0.024% . It also only creates 600 tokens per year extra in inflation. Or only 120 tokens FOR THE WHOLE YEAR that goes towards BP pay.
  3176. 05.06.2018 14:38:20, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We can adjust inflation later to reduce supply , or repay from a Worker Proposal
  3177. 05.06.2018 14:54:37, Ravi (Blockpro.one) [@ravincal]: Are you guys only validating the snapshot or also if things like regProducer works?
  3178. 05.06.2018 14:56:37, James Sutherland - Cypherglass.com [@JamesSutherland]: Both. Data validation and Software function validation
  3179. 05.06.2018 14:57:54, Ravi (Blockpro.one) [@ravincal]: My regProducer call is returning no active private key error.. though wallet is open and private keys are visible there
  3180. 05.06.2018 14:58:20, Ravi (Blockpro.one) [@ravincal]: Check my messages in bios boot channel
  3181. 05.06.2018 14:59:04, Ravi (Blockpro.one) [@ravincal]: New account creation worked without a hitch
  3182. 05.06.2018 14:59:27, Ravi (Blockpro.one) [@ravincal]: But regProducer not working
  3183. .....05.06.2018 15:01:36, Josh Kauffman - EOS Canada [@joshkauff]: >>invited Ovi - eosromania22 - BP [@iamveritas]<<
  3184. 05.06.2018 15:04:12, James Sutherland - Cypherglass.com [@JamesSutherland]: Very busy right now @ravincal but I wil ltry to hook up with you later.
  3185. 05.06.2018 15:05:48, Timothy Lewis [@trustlayer]: If your BP is on this list, MSG me:
  3186.  
  3187. boot.eostitan.com
  3188. ec2-18-188-4-97.us-east-2.compute.amazonaws.com
  3189. m.jeda.one
  3190. api.eosuk.io
  3191. node.eosmeso.io
  3192. prod.mainnet.eos.cybex.io
  3193. ec2-18-188-38-75.us-east-2.compute.amazonaws.com
  3194. fullnode.eoslaomao.com
  3195. 35.234.53.243
  3196. eosboot.chainrift.com
  3197. boot.eostitan.com
  3198. ec2-54-95-202-14.ap-northeast-1.compute.amazonaws.com
  3199. 05.06.2018 15:07:00, Rohan - EOSauthority [@RohanWillAnswer]: Is being on the list a good thing or a bad thing? 🙂
  3200. 05.06.2018 15:07:14, Timothy Lewis [@trustlayer]: no comment.
  3201. 05.06.2018 15:07:20, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: Haha
  3202. 05.06.2018 15:07:25, Rohan - EOSauthority [@RohanWillAnswer]: 😂
  3203. 05.06.2018 15:09:15, Marshall - SaltBlock [@marshallslc]: I can stop sweating now
  3204. 05.06.2018 15:09:20, Andrey Marchuk [@madz7z]: 🙂
  3205. 05.06.2018 15:09:58, Ravi (Blockpro.one) [@ravincal]: Sent you Dm
  3206. 05.06.2018 15:20:43, Craig Murray - EOS BlockSmith [@craigmurray100]: woot! my name didnt show up... 😅
  3207. 05.06.2018 15:21:07, Craig Murray - EOS BlockSmith [@craigmurray100]: also thank you for doing this, very important
  3208. 05.06.2018 15:21:39, Luke Stokes [@lukestokes]: As requested on the Zoom call, here are the screenshots I mentioned of the conversation with Dan. His criteria five days ago:
  3209.  
  3210. 1. Does someone lose money?
  3211.  
  3212. 2. Is there down time?
  3213.  
  3214. 3. Does the chain just pause for 24 hours while we fix it?
  3215.  
  3216. He goes on to say his primary concern is the loss of private keys since we do not have account recovery for these early accounts generated via the snapshot. If we're not dealing with a category 1 or 2 issue, we should be in a pretty good place to launch. Category 3 would be very unfortunate, but something we can recover from. As Dan said 5 days ago "I don't think the current test network is actually invalid" (which would imply it's valid).
  3217. 05.06.2018 15:22:01, Luke Stokes [@lukestokes]: [[Photo]]
  3218. 05.06.2018 15:22:07, James Sutherland - Cypherglass.com [@JamesSutherland]: +1
  3219. 05.06.2018 15:22:14, Luke Stokes [@lukestokes]: [[Photo]]
  3220. 05.06.2018 15:24:40, Luke Stokes [@lukestokes]: Now for my personal opinion: if we don't have mission critical bugs, we should move forward. There will be more bugs discovered in the future in production, regardless of how much sanitized testing we do under lab conditions. Continuing to find bugs this late in the process is certainly concerning, but if they aren't show stoppers, we should be able to deal with it. The best penetration testers I've ever seen come from unconvention sources, not from structured security firms. The sooner we get this out there live, the sooner we'll know what we're really dealing with.
  3221. 05.06.2018 15:28:04, mini - EOS Argentina [@moonxor]: +1 to @lukestokes
  3222. 05.06.2018 15:28:10, Marshall - SaltBlock [@marshallslc]: Agreed. Everyone is anxious to get it launched and tensions are high. I think there may be a misconception that people are searching for bugs blindly, but really are just making sure the software works as intended through the entire process. Once we can be sure everything works as intended I dont think anyone is calling for testing beyond that.
  3223. 05.06.2018 15:28:31, Michael Yeates [@michaelyeates]: 👍
  3224. 05.06.2018 15:28:41, deck - EOS New York [@deckw]: +1
  3225. 05.06.2018 15:28:47, Denis | EOS Nation [@DenisCarriere]: 👍 @lukestokes Thanks for sharing, very valuable information
  3226. 05.06.2018 15:29:05, Joshua Qiu @EOSeco [@Joshuaqiu]: agreed
  3227. 05.06.2018 15:29:55, Luke Stokes [@lukestokes]: I've shared the above message in various channels, but feel free to share further if it's helpful. I'm excited to see this thing launch and then enjoy the wild ride we find ourselves on after that. 🙂
  3228. 05.06.2018 15:30:27, Jae Chung - HKEOS [@jaechung]: 👍
  3229. 05.06.2018 15:37:16, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Excellent thank you
  3230. 05.06.2018 15:42:00, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Just to recap my recommendation:
  3231.  
  3232. A) We continuously improve security of the network (multiple initiatives going on now to help, thanks to @trustlayer @dftle)
  3233.  
  3234. In parallel:
  3235. 1. We agree on the optimal boot sequence (is RAM buying the only issue to solve?)
  3236. 2. We code it (if not already done) and review open source implementation
  3237. 3. We inject it (if not already done) on a swarm of nodes that includes everyone
  3238. 4. We test it (insert Thomas' test report spreadsheet here)
  3239. 5. We select an ABP to hold custody of the network until the 15% vote is done
  3240. 6. We make sure we are all meshed together and help hide the ABP
  3241. 7. We announce validation and voting starts.
  3242.  
  3243. Please note: No one can brag about the software used, being the boot node or the ABP. We just don't care!!
  3244.  
  3245. We are all working together to make this better for the token holders.
  3246. 05.06.2018 15:45:07, mini - EOS Argentina [@moonxor]: +1
  3247. 05.06.2018 15:46:36, Luke Stokes [@lukestokes]: Sounds good to me, though I have had concerns with the "code it" part in the past if it could lead to any possible security concerns. To me, the key step is the validation of the chain. However that chain is created doesn't matter to me as much as it being a valid chain. Once we have a valid chain (regardless of the process), I'm happy to go live with it without caring who created it or how it was created.
  3248. 05.06.2018 15:46:40, Patrick B - Aloha EOS: 👍
  3249. 05.06.2018 15:47:11, Marc-Antoine Ross - EOS Canada [@marcantoineross]: +1
  3250. 05.06.2018 15:53:51, Luke Stokes [@lukestokes]: [[Webpage]]Related to the concerns here Dan mentioend about web portals for voting, I'd like to make sure people know about this desktop voting tool @jestagram created: https://steemit.com/eos/@greymass/announcing-eos-voter-an-eos-block-producer-voting-tool-and-light-wallet
  3251.  
  3252. I've used his Vessel wallet before on STEEM along with many other products he's built over the last (almost) two years. They are soild. I helped him test this on the Jungle Testnet when he first launched it, and it worked well.
  3253.  
  3254. I much prefer independent blockchain applications over the old model of centralized points of failure (website servers which can be hacked, DNS which can be hacked, domains which can be phished, etc). To me, moving our community away from "use this website" to "use this open-source, trusted tool" is a better approach long term.
  3255. 05.06.2018 15:53:58, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: [[Webpage]]BPs doing testing, please join the Zoom testing call at the top of the current hour (in 6 minutes)
  3256. https://zoom.us/j/5788946547
  3257. .....05.06.2018 16:37:52, Timothy Lewis [@trustlayer]: >>invited ndoy |EOS Cafe: Calgary | [@n_doy]<<
  3258. 05.06.2018 16:38:10, ndoy |EOS Cafe: Calgary | [@n_doy]: Thanks @trustlayer !
  3259. 05.06.2018 16:41:13, Roman CryptoLions [@romanskaskiw]: Link to document?
  3260. 05.06.2018 16:41:42, ndoy |EOS Cafe: Calgary | [@n_doy]: Brandon is updating
  3261. 05.06.2018 16:42:38, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Summary of testing meeting:
  3262. 1. All test DEFINITIONS to be entered within 49 minutes of now
  3263. 2. Links to the data entry forms (2) and spreadsheet (1) will be posted here as soon as Branden makes the requested changes
  3264. 3. All test RESULTS to be added ASAP, by 2300 UTC preferred.
  3265. 4. If you have a bunch of results in a file, you can paste a link to the file in the 'results' field -- you don't have to laboriously re-enter old data
  3266. 05.06.2018 16:46:40, Rohan - EOSauthority [@RohanWillAnswer]: Thanks Branden for putting together the document so quickly
  3267. 05.06.2018 16:47:24, Jose Toriello [@josetoriello]: Word.
  3268. 05.06.2018 16:51:22, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Question was posed, "how do I show a user the Constitution? How do I display the relevant Ricardian Contract for an action?"
  3269.  
  3270. Answer for web clients - the web api that lets you serialize JSON to binary should retrieve the JSON ABI of the command, which contains a section [ricardian clauses] which contains what you need. It'll be ugly as-is, so format it using "handlebar" or "moustache" method
  3271.  
  3272. I'm trying to get some sample code to share.
  3273.  
  3274. There's a plan to upgrade CLEOS to do this at the command line and show the user the contract.
  3275. 05.06.2018 16:54:15, Roman CryptoLions [@romanskaskiw]: What's the framing of this whole effort? Is it critical testing before going public with the launch?
  3276.  
  3277. Asking because we don't know how to reconcile the hard deadline with continuous testing we've been doing since April in the Jungle Testnet.
  3278. 05.06.2018 16:56:24, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Please focus on critical tests
  3279. 05.06.2018 16:58:26, Denis | EOS Nation [@DenisCarriere]: 🔔REQUEST: Been in touch with a few Asian BP, they are asking if we can push our 2300 UTC (decision meeting) by +2 hours.
  3280.  
  3281. Most of them are not even awake to receive this message, Mao (EOSReal) is still monitoring Telegram and it's 5am for him.
  3282.  
  3283. EOS Sillicon Valley also mentioned it would be better if we pushed a couple hours.
  3284.  
  3285. ❓PROPOSAL: Have the decision meeting pushed to 0100 UTC Wednesday (June 6)
  3286.  
  3287. 👍/ 👎for moving +2 hours?
  3288. 05.06.2018 17:00:45, Marc-Antoine Ross - EOS Canada [@marcantoineross]: 👍
  3289. 05.06.2018 17:00:55, deck - EOS New York [@deckw]: 👍
  3290. 05.06.2018 17:01:04, Nate D - Aloha EOS [@n8dee]: 👍
  3291. 05.06.2018 17:02:04, Nate D - Aloha EOS [@n8dee]: telegram needs a reaction counter like slack and discord
  3292. 05.06.2018 17:02:56, Branden Espinoza [@espinbrand]: Could I get one person to test the forms really quickly?
  3293. 05.06.2018 17:03:05, deck - EOS New York [@deckw]: tag
  3294. 05.06.2018 17:03:40, Rick Schlesinger - EOS New York [@unlockrs]: 👍 @maoyifeng is a good human
  3295. 05.06.2018 17:03:57, Patrick B - Aloha EOS: 👍
  3296. 05.06.2018 17:05:48, Jose Toriello [@josetoriello]: 👍
  3297. 05.06.2018 17:10:09, deck - EOS New York [@deckw]: Tagging @DavidMoss
  3298. 05.06.2018 17:10:13, Sharif Bouktila - EOS Dublin [@sharifbouktila]: @marcantoineross I've made you an Admin here so you can pin next call details.
  3299. 05.06.2018 17:10:54, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Thanks
  3300. 05.06.2018 17:11:22, Denis | EOS Nation [@DenisCarriere]: [[Photo]]😴
  3301. 05.06.2018 17:11:52, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: [[Webpage]]Enter your tests!
  3302. https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit?usp=sharing
  3303. 05.06.2018 17:11:59, Rohan - EOSauthority [@RohanWillAnswer]: 👍I won’t be able to make it, but I feel Asian BPs need to be kept in the loop
  3304. 05.06.2018 17:16:35, Craig Murray - EOS BlockSmith [@craigmurray100]: 👍
  3305. 05.06.2018 17:18:28, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: @sharifbouktila the 'next validation' call message pinned in this channel is obsolete
  3306. 05.06.2018 17:19:25, Rohan - EOSauthority [@RohanWillAnswer]: Are we ok to have cleos commands for create steps?
  3307. 05.06.2018 17:20:16, Branden Espinoza [@espinbrand]: So long as the procedure to use them is clear to the audience.
  3308. 05.06.2018 17:20:18, deck - EOS New York [@deckw]: @marcantoineross I believe you are admin now
  3309. 05.06.2018 17:21:17, Rohan - EOSauthority [@RohanWillAnswer]: Ok, something like this
  3310. > cleos create account ACC_NAME_GENESIS NEW_ACC EOS_PUB EOS_PUB
  3311.  
  3312. That should be fairly easy for most people to understand.. the capital letters need to be replaced in..
  3313. 05.06.2018 17:21:17, Branden Espinoza [@espinbrand]: So long as the procedure to use them is clear to the audience. The idea is to keep the Steps as process oriented as possible.
  3314. 05.06.2018 17:21:36, Sharif Bouktila - EOS Dublin [@sharifbouktila]: @marcantoineross will pin next one, I won’t make it.
  3315. 05.06.2018 17:21:44, Rohan - EOSauthority [@RohanWillAnswer]: Yes, I like to have ready to execute commands, much easier to compelte them all..
  3316. 05.06.2018 17:21:55, Branden Espinoza [@espinbrand]: Out of my world of expertise.
  3317. 05.06.2018 17:22:48, Rohan - EOSauthority [@RohanWillAnswer]: If we say create an account, its not clear what is being tested.. Specific commands will be easier? I will keep adding it that way.. maybe a note on what it is intended to do followed by the command.
  3318. 05.06.2018 17:23:15, Branden Espinoza [@espinbrand]: So long as the procedure to use them is clear to the audience.
  3319. 05.06.2018 17:23:24, Branden Espinoza [@espinbrand]: sorry... didn't mean to post that again.
  3320. 05.06.2018 17:23:25, Branden Espinoza [@espinbrand]: lol
  3321. 05.06.2018 17:24:00, Branden Espinoza [@espinbrand]: I sincerely hope the tool helps. I'm logging off for about 2 hours. I will check back as soon as I can to address any issues.
  3322. 05.06.2018 17:30:44, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: [[Webpage]]Testing Zoom call in 5 minutes, at 21:35 UTC
  3323. https://zoom.us/j/5788946547
  3324. 05.06.2018 17:31:58, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Folks engaged in testing, please hop on -- I have a question from Bart and Arhag about the testing method, there's a concern that certain approaches might create spurious errors
  3325. 05.06.2018 17:34:33, deck - EOS New York [@deckw]: @abourget @michaelyeates @ eric
  3326. 05.06.2018 17:35:16, Roman CryptoLions [@romanskaskiw]: @xebb82
  3327. 05.06.2018 17:35:23, deck - EOS New York [@deckw]: yea that one haha
  3328. 05.06.2018 17:35:26, Roman CryptoLions [@romanskaskiw]: 😊
  3329. 05.06.2018 17:35:45, deck - EOS New York [@deckw]: @igorls
  3330. .....05.06.2018 17:42:10, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  3331. 05.06.2018 17:52:16, Sam - EOS Dublin [@samnoble]: Are we all in agreement that we are moving THE CALL from 2300 UTC to 0100 UTC? I haven't seen any objections yet.
  3332. 05.06.2018 17:53:36, Gustavo Mick - EOS Argentina [@gustavomick]: Eos argentina agrees
  3333. 05.06.2018 17:53:37, David Moss [@DavidMoss]: 9am Wednesday China time. Definitely want Asia to participate here
  3334. 05.06.2018 17:56:38, Branden Espinoza [@espinbrand]: After you submit a case, you are taken to a page that includes a link to edit your case. You should bookmark that link for each case since it is the only means you have to edit a case once it is submitted.
  3335. 05.06.2018 17:56:44, James Sutherland - Cypherglass.com [@JamesSutherland]: Works for me. Please pin that if it's for real.
  3336. 05.06.2018 17:56:54, James Sutherland - Cypherglass.com [@JamesSutherland]: If it becomes real I mean
  3337. 05.06.2018 17:59:48, Marc-Antoine Ross - EOS Canada [@marcantoineross]: ALL: Next zoom call at 0100UTC to review test results and agree on plan
  3338. .....05.06.2018 17:59:57, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  3339. 05.06.2018 18:00:04, James Sutherland - Cypherglass.com [@JamesSutherland]: +1
  3340. 05.06.2018 18:07:45, mini - EOS Argentina [@moonxor]: +1
  3341. 05.06.2018 18:27:35, deck - EOS New York [@deckw]: Validation call with Aarin Hagerty(edited for correct spelling)
  3342.  
  3343. Pausing the chain is dangerous because there a potential to fork, if keys are shared and/or we have a rogue ABP. After 15%, everyone can fix a checkpoint at the first schedule, making that key irrelevant for eternity.
  3344.  
  3345. Having defined process for injection and validation on a testnet is sufficient to get high degree of confidence that a mainnet using the same process, validation being rerun, is good.
  3346.  
  3347. Two options:
  3348. Throw all current mainnet candidates out after testing is complete and recreate using the deterministic approaches we have. We would validate the boot sequence and the state right after. (recommended)
  3349. Reuse the chain we have been testing and allow this potential issue to remain
  3350.  
  3351. Testing delayed transactions would be interesting.
  3352. 05.06.2018 18:47:43, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: Throw all current mainnet candidates out after testing is complete and recreate using the deterministic approaches we have.
  3353. <- 👏👏👏👏👏👏👏
  3354. 05.06.2018 18:48:48, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: that would throw all "ego" away about any opinion of bios/gb chain, and launch a unified mainnet together.
  3355. 05.06.2018 19:02:22, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: [[Webpage]]Arhag, often goes by Aarin Hagerty, various spellings. Github is "https://github.com/arhag"
  3356. 05.06.2018 19:03:30, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: [[Webpage]]Please enter test results!
  3357. Please enter test results!
  3358. Please enter test results!
  3359. https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit#gid=1501553294
  3360. 05.06.2018 19:07:40, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Honestly I thought this was all done during all those dry runs everyone was doing, but can't turn back the clock now. I agree if we're happy with acceptance testing and have an agreed validation test, it makes sense if the code hasn't changed, re-start, validate, open tx
  3361. 05.06.2018 19:11:27, deck - EOS New York [@deckw]: The 'nice' thing about restarting the chain is it gives us the oppurtunity to decided on the method of paying for RAM at launch. One group or the other can launch, freeze for N hours, allow for everyone to mesh, validate (much like the snapshot), and report results. It might just work out :)
  3362. 05.06.2018 19:11:47, Timothy Lewis [@trustlayer]: +1
  3363. 05.06.2018 19:12:10, Craig Murray - EOS BlockSmith [@craigmurray100]: we already have one ready for tx though, why does that need restarted?
  3364. 05.06.2018 19:12:35, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Have we run the UAT against a copy of that chain?
  3365. 05.06.2018 19:12:52, Timothy Lewis [@trustlayer]: Have we had a well done voting tool at all during this?
  3366. 05.06.2018 19:13:06, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Just need to make sure we tighten up the timelines
  3367. 05.06.2018 19:13:39, Nathan Rempel | GenerEOS Sydney [@nsrempel]: like, UAT is done, we have 2 hours to boot, 2 hours to validate, if everyone checks in good, send it
  3368. 05.06.2018 19:14:46, deck - EOS New York [@deckw]: I believe that eosportal was tested against a Core testnet
  3369. 05.06.2018 19:15:06, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Only 13 test cases added so far.
  3370. ZERO test results added so far.
  3371. Please pick up the pace.
  3372. 05.06.2018 19:15:06, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Can i throw some of the latest firestarter results in here i should ido that elsewhere?
  3373. 05.06.2018 19:15:42, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: check your PMs
  3374. 05.06.2018 19:16:08, mini - EOS Argentina [@moonxor]: @zhaoyu did some testing, dont know if they put it in the sheet, but they have already test a lot of things.
  3375. 05.06.2018 19:16:40, Craig Murray - EOS BlockSmith [@craigmurray100]: yeah the chain B has 2.5 days of testing already, there was a spreadsheet for that, not sure what happened to all that 😢
  3376. 05.06.2018 19:17:08, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Does the DaoMao test incude any/many/all of those 13 cases?
  3377. 05.06.2018 19:18:11, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: If you can find it, paste the link in to the test results form. No reinventing wheels here please
  3378. 05.06.2018 19:18:31, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: They may not know about the form yet.
  3379. 05.06.2018 19:19:35, mini - EOS Argentina [@moonxor]: [[Webpage]]https://github.com/eoslaomao/eos-cluster-generator
  3380. 05.06.2018 19:19:35, Craig Murray - EOS BlockSmith [@craigmurray100]: Dublin would know they were doing all the record keeping. I'm fighting with this private network wireguard mesh situation trying to find the correct fork for each of my nodes
  3381. 05.06.2018 19:19:55, mini - EOS Argentina [@moonxor]: Conclusion
  3382.  
  3383. 1 The voting works as expected.
  3384. 2 The delegatebw and undelegatebw works as expected.
  3385. 3 The network needs to reach 15% votings, until then, you cannot unstake all tokens.
  3386. 4 staked tokens weather be used for voting or not, both can be unstaked after 15% voting readched.
  3387. 05.06.2018 19:20:00, mini - EOS Argentina [@moonxor]: from their repo
  3388. 05.06.2018 19:20:21, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Outstanding. Please PM me the link to their repo
  3389. 05.06.2018 19:20:22, mini - EOS Argentina [@moonxor]: yes probably
  3390. 05.06.2018 19:22:58, Nathan Rempel | GenerEOS Sydney [@nsrempel]: [[Webpage]]how quickly can someone update https://github.com/eoslaomao/eos-cluster-generator to cover the remaning UATs?
  3391. 05.06.2018 19:24:25, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i can start writing an eosjs for the non-time sensitive test cases too if no one has yet, or are we running manual commands?
  3392. 05.06.2018 19:25:58, mao EOSREAL [@maoyifeng]: chinese bpcs confirming the call 1.5 hours ahead and are discussing their stands.
  3393. 05.06.2018 19:37:02, Jose Toriello [@josetoriello]: Please specify what time you mean?
  3394. 05.06.2018 19:37:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I'm currently writing a supplment document with all the cleos commands to run to match the test cases and what the expected results should be
  3395. 05.06.2018 19:37:35, Nathan Rempel | GenerEOS Sydney [@nsrempel]: BPs can manually run them if they wish and add to the form
  3396. 05.06.2018 19:37:42, mao EOSREAL [@maoyifeng]: Roughly 1.5 hours ahead. 9pm est.
  3397. 05.06.2018 19:42:09, WinLin-EOSBIXIN [@hiwinlin]: 👍
  3398. 05.06.2018 19:51:54, WinLin-EOSBIXIN [@hiwinlin]: to be honest most case in the execel doc, many of Chinese BPs have finished since Dawn-v4.2 and many times test in v1.0.1
  3399. 05.06.2018 19:52:10, Nathan Rempel | GenerEOS Sydney [@nsrempel]: The UAT document seems a little schewed, like Case RAM market has name bidding..
  3400. 05.06.2018 19:57:17, Nathan Rempel | GenerEOS Sydney [@nsrempel]: [[Webpage]]Ok guys here's a supplement document: https://docs.google.com/document/d/1qFEUt3Z-sy8-vWrzmoH-TjXE6850_4lCpdzBoDaj4A0/edit?usp=sharing
  3401. 05.06.2018 19:57:57, Nathan Rempel | GenerEOS Sydney [@nsrempel]: This is so individual BPs or "anyone" can run the UAT tests by command line. Please continue to add commands for each test case as appropriate
  3402. 05.06.2018 19:58:48, Nathan Rempel | GenerEOS Sydney [@nsrempel]: some of the latest UATs will require scripts to be run, however I see several are from @BohdanCryptoLions
  3403. 05.06.2018 19:59:09, Nathan Rempel | GenerEOS Sydney [@nsrempel]: If @BohdanCryptoLions has been running against release-rc or v1.0.1 perhaps you can publish those results
  3404. 05.06.2018 19:59:23, mini - EOS Argentina [@moonxor]: awesome work!
  3405. .....05.06.2018 20:01:43, Nate D - Aloha EOS [@n8dee]: >>invited Peter Bue | EOSAmericas<<
  3406. .....05.06.2018 20:02:43, Peter Bue | EOSAmericas: >>invited Ed Silva [@edeosamericas]<<
  3407. 05.06.2018 20:20:03, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: 👍😁
  3408. 05.06.2018 20:20:23, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: 👍😁❤️
  3409. 05.06.2018 20:20:50, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Wonderful.
  3410. 05.06.2018 20:23:23, WinLin-EOSBIXIN [@hiwinlin]: yes, Asia bp teams have done lots things but someone always choose to ignore this
  3411. 05.06.2018 20:23:35, WinLin-EOSBIXIN [@hiwinlin]: this is unfair
  3412. 05.06.2018 20:24:22, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I don't think the community is ignoring, do you have documentation that test was run? Please, PLEASE share!
  3413. 05.06.2018 20:28:15, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: I don't think it's ignoring, so much as cluelessness. I hang my head in shame
  3414. 05.06.2018 20:30:01, WinLin-EOSBIXIN [@hiwinlin]: [[Webpage]]thanks all
  3415. the validation tool :https://github.com/EOSBIXIN/eostoolkit/tree/master/eos_validator
  3416. 05.06.2018 20:30:29, WinLin-EOSBIXIN [@hiwinlin]: this tool support eos-bios and manula startup chain
  3417. 05.06.2018 20:30:32, WinLin-EOSBIXIN [@hiwinlin]: both
  3418. 05.06.2018 20:30:33, Nathan Rempel | GenerEOS Sydney [@nsrempel]: for all the chinese BP that have used this tool, do you have a document showing the output?
  3419. 05.06.2018 20:30:51, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Yes it would be great to see validation from Asia
  3420. 05.06.2018 20:30:55, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: So we can record that
  3421. 05.06.2018 20:31:16, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Right now, its only BIXIN and a handful that we have seen
  3422. 05.06.2018 20:31:22, WinLin-EOSBIXIN [@hiwinlin]: [[Photo]]
  3423. 05.06.2018 20:31:22, WinLin-EOSBIXIN [@hiwinlin]: like this
  3424. 05.06.2018 20:31:33, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: That is run by you though
  3425. 05.06.2018 20:31:38, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: We mean other Asian BPCs
  3426. 05.06.2018 20:31:47, WinLin-EOSBIXIN [@hiwinlin]: [[Photo]]
  3427. 05.06.2018 20:32:22, WinLin-EOSBIXIN [@hiwinlin]: wait please, it is too early I will find some bp to prove
  3428. 05.06.2018 20:32:30, WinLin-EOSBIXIN [@hiwinlin]: @zhaoyu from EOSLAOMAO
  3429. 05.06.2018 20:33:06, WinLin-EOSBIXIN [@hiwinlin]: @Joshuaqiu from ESOSeco
  3430. 05.06.2018 20:33:17, WinLin-EOSBIXIN [@hiwinlin]: @dftle from eosAsia
  3431. 05.06.2018 20:33:31, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Yes we have those 3, they are vocal in calls as well
  3432. 05.06.2018 20:33:36, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: We were wondering if theres anyone else
  3433. 05.06.2018 20:33:40, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: We have missed?
  3434. 05.06.2018 20:38:33, Alexandre Bourget - EOS Canada [@abourget]: WinLin was the first to write a validation tool, first to publish reports and I think he has the most complete validation took to date.
  3435.  
  3436. He published his results time and time again and helped identify issues in the first 3 iterations of a mainnet candidate.
  3437.  
  3438. I am truly grateful for your work WinLin
  3439. 05.06.2018 20:39:18, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 👍👍👍
  3440. 05.06.2018 20:41:16, WinLin-EOSBIXIN [@hiwinlin]: we all support EOS and want to make her more valueable, so let's move on and introdcue her into the world
  3441. 05.06.2018 20:41:21, Luke Stokes [@lukestokes]: Has anyone else created a currency contract yet? I tried created the eosDAC one on Jungle and it blew up. Might just be our contract is bad, but I wanted to ask here before I ask in Jungle.
  3442. 05.06.2018 20:41:45, Nate D - Aloha EOS [@n8dee]: 👍
  3443. 05.06.2018 20:42:01, WinLin-EOSBIXIN [@hiwinlin]: yes, I have created some token in dawn v-4.2
  3444. 05.06.2018 20:42:08, Peter Bue | EOSAmericas: 👍👍
  3445. 05.06.2018 20:42:30, WinLin-EOSBIXIN [@hiwinlin]: so there should be some wrong in you env,please chekc again
  3446. 05.06.2018 20:42:36, Luke Stokes [@lukestokes]: Thanks. I'll dig into main.cpp at line 2584 to see what's broken. 🙂
  3447. 05.06.2018 20:43:02, Luke Stokes [@lukestokes]: I had an earlier issue with boost, so it surely could be my local env. Thanks.
  3448. 05.06.2018 20:44:39, Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer [@tyeenoprom]: Tyee from EOSpace
  3449. 05.06.2018 20:44:53, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 👍
  3450. 05.06.2018 20:44:58, WinLin-EOSBIXIN [@hiwinlin]: [[Webpage]]you can take a look about the EOSLaoMao tool:https://github.com/EOSLaoMao/eos-cluster-generator
  3451. 05.06.2018 20:45:35, Luke Stokes [@lukestokes]: thanks. I haven't played with that yet, but it looks really interesting
  3452. 05.06.2018 20:46:03, WinLin-EOSBIXIN [@hiwinlin]: yes, that's very intreasting
  3453. .....05.06.2018 20:47:07, Gordo | HelloEOS [@gordoor]: >>unsupported service message type: messageActionChatJoinedByLink<<
  3454. 05.06.2018 20:51:46, Branden Espinoza [@espinbrand]: Many of you know my role in this. Is there any value in me attending the next zoom call?
  3455. 05.06.2018 20:52:57, Branden Espinoza [@espinbrand]: Maybe a better question for @thomasbcox
  3456. 05.06.2018 20:53:43, Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer [@tyeenoprom]: You can use this tool to validate yourself.
  3457. 05.06.2018 20:53:55, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: No
  3458. 05.06.2018 20:53:59, Joshua Qiu @EOSeco [@Joshuaqiu]: i have another , but only check balance
  3459. 05.06.2018 20:54:14, Branden Espinoza [@espinbrand]: TY.
  3460. 05.06.2018 20:54:27, Gordo | HelloEOS [@gordoor]: We've been using WinLin's tool to do the validation
  3461. 05.06.2018 20:55:31, Tyee Noprom | EOSBlock.co | EOSpace.io | EOS Committer [@tyeenoprom]: That's fine. You can use your own tool to validate both chains.
  3462. 05.06.2018 20:56:50, Joshua Qiu @EOSeco [@Joshuaqiu]: [[Webpage]]https://github.com/qiushaoxi/eos-validation snapshot balance are fine on both side
  3463. 05.06.2018 20:57:41, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Ok guys, in advance of this call I have created a survey so we can get some "real documented concensus" rather than everyone speaking up in a call
  3464. 05.06.2018 20:57:42, Nathan Rempel | GenerEOS Sydney [@nsrempel]: [[Webpage]]https://goo.gl/forms/D8M7c5QFyMCwmCaF2
  3465. 05.06.2018 20:58:27, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I'd appreciate if someone could review it quickly if there's anything that should be added
  3466. 05.06.2018 20:58:51, deck - EOS New York [@deckw]: I believe the suggested time to launch was tomorrow at 1300 utc
  3467. 05.06.2018 20:59:06, Nathan Rempel | GenerEOS Sydney [@nsrempel]: oops my bad
  3468. 05.06.2018 20:59:15, deck - EOS New York [@deckw]: np good work putting this together
  3469. 05.06.2018 20:59:19, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I dont think we can reverse chain probably, do you mean load from backup?
  3470. 05.06.2018 20:59:22, Nathan Rempel | GenerEOS Sydney [@nsrempel]: mixing up my time zone
  3471. 05.06.2018 20:59:48, deck - EOS New York [@deckw]: @marcantoineross Can you post the zoom link
  3472. 05.06.2018 20:59:52, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]All, here the proposed flow for the call
  3473.  
  3474. A) We continuously improve security of the network (multiple initiatives going on now to help, thanks to @trustlayer @dftle)
  3475.  
  3476. In parallel:
  3477. 1. We agree on the optimal boot sequence (is RAM buying the only issue to solve?)
  3478. 2. We code it (if not already done) and review open source implementation
  3479. 3. We inject it (if not already done) on a swarm of nodes that includes everyone
  3480. 4. We test it (insert Thomas' test report spreadsheet here)
  3481. 5. We select an ABP to hold custody of the network until the 15% vote is done
  3482. 6. We make sure we are all meshed together and help hide the ABP
  3483.  
  3484. https://zoom.us/j/681388230
  3485. .....05.06.2018 20:59:59, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  3486. 05.06.2018 21:01:08, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Yes
  3487. 05.06.2018 21:01:19, Nathan Rempel | GenerEOS Sydney [@nsrempel]: basically "restart"
  3488. 05.06.2018 21:13:41, Timothy Lewis [@trustlayer]: Guys the call is at max participants
  3489. 05.06.2018 21:14:07, Denis | EOS Nation [@DenisCarriere]: 🤔 I'll let people know about this
  3490. 05.06.2018 21:14:20, Craig Murray - EOS BlockSmith [@craigmurray100]: i thought someone with a 200 max was going to create?
  3491. 05.06.2018 21:14:28, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Are we having 1 BP rep in the call? I know there is a lot of BP candidates
  3492. 05.06.2018 21:16:12, Timothy Lewis [@trustlayer]: No one from my team is in the call and I would like to be.
  3493. 05.06.2018 21:16:28, Andrey Marchuk [@madz7z]: there are 2 spots
  3494. 05.06.2018 21:16:29, Nathan Rempel | GenerEOS Sydney [@nsrempel]: they are working to expand to 200
  3495. 05.06.2018 21:16:30, Andrey Marchuk [@madz7z]: try now
  3496. 05.06.2018 21:16:31, Nathan Rempel | GenerEOS Sydney [@nsrempel]: some open spaces now
  3497. 05.06.2018 21:16:53, Timothy Lewis [@trustlayer]: sweet
  3498. 05.06.2018 21:16:54, Timothy Lewis [@trustlayer]: ty
  3499. 05.06.2018 21:35:23, James Sutherland - Cypherglass.com [@JamesSutherland]: 200 people allowed now
  3500. 05.06.2018 21:35:42, James Sutherland - Cypherglass.com [@JamesSutherland]: Nice job @marcantoineross !
  3501. 05.06.2018 21:37:03, Denis | EOS Nation [@DenisCarriere]: 👨‍👩‍👧‍👧 more people allowed!
  3502. 05.06.2018 21:37:34, James Sutherland - Cypherglass.com [@JamesSutherland]: Please mute yourself
  3503. 05.06.2018 21:37:58, James Sutherland - Cypherglass.com [@JamesSutherland]: Stay muted until you need to speak
  3504. .....05.06.2018 22:29:38, Ren Kaidi - EOSWTZ [@FoxMr]: >>invited Jialin Li - EOS WTZ [@Jialinli]<<
  3505. 05.06.2018 22:31:06, Alex - EOS SOCAL [@gmory]: Did the call just die?
  3506. 05.06.2018 22:31:13, Nathan Rempel | GenerEOS Sydney [@nsrempel]: non
  3507. 05.06.2018 22:31:21, James Sutherland - Cypherglass.com [@JamesSutherland]: I am still on
  3508. 05.06.2018 22:31:49, James Sutherland - Cypherglass.com [@JamesSutherland]: 138 people connected
  3509. 05.06.2018 22:33:57, deck - EOS New York [@deckw]: @marcantoineross do it
  3510. 05.06.2018 22:34:03, deck - EOS New York [@deckw]: I vote @marcantoineross
  3511. 05.06.2018 22:39:15, Alexandre Bourget - EOS Canada [@abourget]: Great call tonight folks
  3512. 05.06.2018 22:39:42, Gustavo Mick - EOS Argentina [@gustavomick]: @abourget could you summarize results from the meeting, thanks
  3513. 05.06.2018 22:40:15, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Can we get a group made for the Asian security audit coordination asap
  3514. 05.06.2018 22:40:32, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Remarkably productive, all things considered. Many thanks to @marcantoineross for hosting
  3515. 05.06.2018 22:40:43, mini - EOS Argentina [@moonxor]: +1 to this
  3516. 05.06.2018 22:42:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: @bo_eossv
  3517. 05.06.2018 22:42:50, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: @eosnewyork, we also need a global statement for this security delay
  3518. .....05.06.2018 22:43:02, Nathan Rempel | GenerEOS Sydney [@nsrempel]: >>invited Bo - EOS Silicon Valley [@bo_eossv]<<
  3519. 05.06.2018 22:43:48, Gustavo Mick - EOS Argentina [@gustavomick]: We need a summary of the meeting for those who have not been able to be there.
  3520. 05.06.2018 22:43:52, Chitty 🅑 - EOS Argentina [@JChitty]: Did I understand correctly that EOS BIOS will launch and EOS Core will appoint the ABPs... right?
  3521. 05.06.2018 22:44:05, Andrey Marchuk [@madz7z]: productive call, thank you!
  3522. 05.06.2018 22:44:07, Nathan Rempel | GenerEOS Sydney [@nsrempel]: No..?
  3523. 05.06.2018 22:44:18, Nathan Rempel | GenerEOS Sydney [@nsrempel]: what do you mean appoint?
  3524. 05.06.2018 22:45:10, Chitty 🅑 - EOS Argentina [@JChitty]: mmm, I guess we will wait for the votes to be counted.. I believe the question was SHOULD WE RESTART A NEW CHAIN, INJECTED WITH THE CURRENT 579a CONTENTS. AND HAVE GHOSTBUSTER RUN ABP TO 15% UNLOCK ?
  3525. 05.06.2018 22:45:33, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i thought that question was discarded
  3526. 05.06.2018 22:45:48, Chitty 🅑 - EOS Argentina [@JChitty]: why?
  3527. 05.06.2018 22:46:20, Craig Murray - EOS BlockSmith [@craigmurray100]: because JEM declined on behalf of ghostbusters to do so, he was not particularly interested in that
  3528. 05.06.2018 22:46:38, Chitty 🅑 - EOS Argentina [@JChitty]: Did Jem represent all of Ghostbuster?
  3529. 05.06.2018 22:46:43, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I believe the final was for everyone to join 579a chain once it passes security check phase
  3530. 05.06.2018 22:47:24, Craig Murray - EOS BlockSmith [@craigmurray100]: 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.
  3531. 05.06.2018 22:47:47, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: They offerred to join as every other BPC
  3532. 05.06.2018 22:48:08, Craig Murray - EOS BlockSmith [@craigmurray100]: yes, they offered to join as ordinary BPCs and not be the ABP
  3533. 05.06.2018 22:48:09, Bo - EOS Silicon Valley [@bo_eossv]: Sure!
  3534. 05.06.2018 22:48:09, Chitty 🅑 - EOS Argentina [@JChitty]: Ok, I must have missed that.. will wait on the report
  3535. 05.06.2018 22:49:17, Luke Stokes [@lukestokes]: One person representing multiple BPCs seemed counter to DPOS to me, but I'm glad we worked through things and got consensus. Great meeting.
  3536. 05.06.2018 22:49:50, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: You mean proxying votes is counter to DPOS?
  3537. 05.06.2018 22:49:55, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Thats a first
  3538. 05.06.2018 22:50:03, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: They delegated their votes
  3539. 05.06.2018 22:50:05, Luke Stokes [@lukestokes]: No, proxy is fine if it's on chain and known
  3540. 05.06.2018 22:50:07, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 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
  3541. .....05.06.2018 22:50:54, Nathan Rempel | GenerEOS Sydney [@nsrempel]: >>invited Hugo Yang - EOS Silicon Valley [@hugo_eossv]<<
  3542. 05.06.2018 22:51:00, David P - EOS42 [@GunnisonCap]: Given the timezone of the vote, a proxy representative makes sense in the same way Bo was for multiple BP's
  3543. 05.06.2018 22:51:08, Luke Stokes [@lukestokes]: Thanks for clarifying that's an arangement (via proxy) people are comfortable with
  3544. 05.06.2018 22:53:14, Igor Lins e Silva - EOS Rio [@igorls]: 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
  3545. 05.06.2018 22:54:13, Nathan Rempel | GenerEOS Sydney [@nsrempel]: @bo_eossv @hugo_eossv Is there a testnet already existing or do you need the community to start one?
  3546. 05.06.2018 22:54:28, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: could we use jungle?
  3547. 05.06.2018 22:54:35, Igor Lins e Silva - EOS Rio [@igorls]: +1
  3548. 05.06.2018 22:54:44, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Well, I thought the idea would be to run it against a clone of our candidate
  3549. 05.06.2018 22:54:51, Nathan Rempel | GenerEOS Sydney [@nsrempel]: but as long as the code is the code
  3550. 05.06.2018 22:54:59, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 🤷‍♂️
  3551. 05.06.2018 22:56:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 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
  3552. 05.06.2018 22:56:52, Nate D - Aloha EOS [@n8dee]: I thought the idea was to start one on production infrastructure
  3553. 05.06.2018 22:56:58, Nate D - Aloha EOS [@n8dee]: But yes, needs clarification.
  3554. 05.06.2018 22:57:20, Nathan Rempel | GenerEOS Sydney [@nsrempel]: That was my understanding also, so Im eager to swtich our production over to this test
  3555. .....05.06.2018 22:57:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: >>invited Dr Ye EOS WashingtonDC - TChain [@doc309]<<
  3556. 05.06.2018 22:57:51, Bo - EOS Silicon Valley [@bo_eossv]: Let me do a quick check
  3557. 05.06.2018 22:58:05, Ren Kaidi - EOSWTZ [@FoxMr]: 👍
  3558. .....05.06.2018 22:59:47, Ren Kaidi - EOSWTZ [@FoxMr]: >>invited Xueyuan She_EOS_WTZ [@xueyuanshe]<<
  3559. 05.06.2018 22:59:55, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: +1
  3560. 05.06.2018 23:00:22, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Is someone already preparing a joint statement to the community regarding the eosio issuance of tokens to gift the genesis accounts with free ram?
  3561. 05.06.2018 23:01:51, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Cypherglass offered to do a video
  3562. 05.06.2018 23:01:54, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: @finchify
  3563. 05.06.2018 23:02:54, Nathan Rempel | GenerEOS Sydney [@nsrempel]: It would be great if we could get a joint steemit/etc to include and share the video
  3564. 05.06.2018 23:02:56, Dr Ye EOS WashingtonDC - TChain [@doc309]: 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
  3565. 05.06.2018 23:04:45, Dafeng Guo - EOS Asia [@dftle]: Details will be coming out soon. Things are rolling.
  3566. 05.06.2018 23:04:57, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Thanks for that
  3567. 05.06.2018 23:05:02, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Thanks Dafeng, keep us updated!
  3568. 05.06.2018 23:06:13, Bo - EOS Silicon Valley [@bo_eossv]: 👍👍
  3569. 05.06.2018 23:07:45, Dr Ye EOS WashingtonDC - TChain [@doc309]: please get tchain posted
  3570. 05.06.2018 23:08:21, Kevin Rose - EOS New York [@eosnewyork]: We’ve already issued it
  3571. 05.06.2018 23:08:36, Kevin Rose - EOS New York [@eosnewyork]: The statement today states the time needed
  3572. 05.06.2018 23:08:55, Kevin Rose - EOS New York [@eosnewyork]: [[Webpage]]https://steemit.com/eos/@eosnewyork/the-eos-mainnet-launch-security-and-software-testing
  3573. 05.06.2018 23:08:56, Dafeng Guo - EOS Asia [@dftle]: 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.
  3574. 05.06.2018 23:09:38, Timothy Lewis [@trustlayer]: Great post.
  3575. 05.06.2018 23:09:43, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: 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
  3576. 05.06.2018 23:09:57, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: Would be nice to reach out to him @BohdanCryptoLions
  3577. 05.06.2018 23:10:23, Kevin Rose - EOS New York [@eosnewyork]: Group effort. Thanks Tim. If you haven’t posted already please feel free to. This is a statement meant to represent us all.
  3578. 05.06.2018 23:11:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: +1
  3579. 05.06.2018 23:15:53, Jose Toriello [@josetoriello]: +1+1
  3580. 05.06.2018 23:16:00, Jose Toriello [@josetoriello]: +1
  3581. 05.06.2018 23:20:30, Luke Stokes [@lukestokes]: I was thinking the same thing. That post covered what we ended up deciding on the call quite nicely. Well done!
  3582. 05.06.2018 23:21:17, Dr Ye EOS WashingtonDC - TChain [@doc309]: +1 happy to help if he Bohdan agrees to take the job
  3583. 05.06.2018 23:23:31, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Any other candidates to spin up this testnet if @BohdanCryptoLions isn't available?
  3584. 05.06.2018 23:25:56, mini - EOS Argentina [@moonxor]: I think eos.host was quite good, dont know if those guys are up for it
  3585. 05.06.2018 23:26:24, mini - EOS Argentina [@moonxor]: the monitor was superv, and they have account creation and a super nice voting system
  3586. 05.06.2018 23:27:16, Dafeng Guo - EOS Asia [@dftle]: I contacted EOS.host yesterday
  3587. 05.06.2018 23:27:51, Dafeng Guo - EOS Asia [@dftle]: They are happy to help
  3588. 05.06.2018 23:28:11, Craig Murray - EOS BlockSmith [@craigmurray100]: nice job staying away from calling out these launch cohorts by name. Well done sir, thanks
  3589. 05.06.2018 23:28:47, mini - EOS Argentina [@moonxor]: great!
  3590. 05.06.2018 23:35:01, Crystal Rose | ⚡️SENSE | 💜shEOS [@crystalrose]: 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! 🙏
  3591. 05.06.2018 23:37:04, Branden Espinoza [@espinbrand]: 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.
  3592. 05.06.2018 23:53:15, Bo - EOS Silicon Valley [@bo_eossv]: Thanks so much everyone for making EOS possible! Really appreciate it👍
  3593. 05.06.2018 23:53:35, Bo - EOS Silicon Valley [@bo_eossv]: 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!
  3594. 05.06.2018 23:54:09, Patrick B - Aloha EOS: Thanks to you as well Bo!
  3595. .....06.06.2018 00:05:43, Mark-eosantpool [@mark_cike]: >>invited Mr.Z [@zlajoni]<<
  3596. 06.06.2018 00:08:23, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]All,
  3597.  
  3598. Thanks for the productive call.
  3599.  
  3600. Find below the minutes, if you find anything not accurate, please suggest/comment and we will fix.
  3601. The raw log is included at the bottom of the document.
  3602.  
  3603. https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c
  3604.  
  3605. Next steps:
  3606. June 6, 1300 UTC: to get consensus on remaining points not covered yet
  3607. Test plan & timeline
  3608. ABP selection
  3609. Meshing and ABP protection
  3610. More?
  3611. June 7, 0100 UTC: the next go/no go discussion, hopefully with the initial security report in hand
  3612.  
  3613. Thanks, good after-mor-night!
  3614. .....06.06.2018 00:08:42, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  3615. 06.06.2018 00:09:18, Daniel Larimer [@daniellarimer]: That’s 1337.
  3616. 06.06.2018 00:09:50, David Moss [@DavidMoss]: Ah, interesting. I heard it different.
  3617. 06.06.2018 00:09:54, David Moss [@DavidMoss]: Still, a rounding error.
  3618. 06.06.2018 00:10:11, David Moss [@DavidMoss]: Printing tokens for RAM startup is a rounding error as well.
  3619. 06.06.2018 00:12:25, Timothy Lewis [@trustlayer]: @abourget @marcantoineross did anyone try to implement the RAM cost solution from K Kim of EOSeoul?
  3620. 06.06.2018 00:12:26, Timothy Lewis [@trustlayer]: [[Webpage]]https://gist.github.com/redjade/c22b2d7fcab068af67c0de31724eb710
  3621. 06.06.2018 00:13:43, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: any post about the whole idea?
  3622. 06.06.2018 00:14:24, Timothy Lewis [@trustlayer]: From the authoer @resvera: "It compiles well. I didn’t test it. I’m not quite expert on boot sequences. But a developer.
  3623.  
  3624. 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.
  3625.  
  3626. This action is very delicate one. Test should include code reviews and actual push action test."
  3627. 06.06.2018 00:22:11, Jose Toriello [@josetoriello]: I suggest "issuing" and not "printing" as a better vocabulary, especially given the sensitivity around the subject.
  3628. 06.06.2018 00:22:15, James Sutherland - Cypherglass.com [@JamesSutherland]: Nice work on this. Thanks for taking the effort to put this document togeather.
  3629. 06.06.2018 00:22:26, Jose Toriello [@josetoriello]: +1
  3630. 06.06.2018 00:22:38, Jose Toriello [@josetoriello]: +1
  3631. 06.06.2018 00:22:48, Jose Toriello [@josetoriello]: +1
  3632. 06.06.2018 00:26:59, Timothy Lewis [@trustlayer]: 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?
  3633. 06.06.2018 00:27:30, David Moss [@DavidMoss]: I agree it's a good solution. Would it require restarting the mainnet candidate>?
  3634. 06.06.2018 00:27:50, Timothy Lewis [@trustlayer]: It would require a code review first, and then a test.
  3635. 06.06.2018 00:28:10, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 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
  3636. 06.06.2018 00:29:34, Timothy Lewis [@trustlayer]: If the test was successful then we would have the opportunity to walk through the boot process as a community.
  3637. 06.06.2018 00:31:08, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Have you run his code and tested it?
  3638. 06.06.2018 00:31:21, Timothy Lewis [@trustlayer]: We are talking about 2-3 hours to complete a test. I have not run it. It needs to be tested.
  3639. 06.06.2018 00:32:05, Timothy Lewis [@trustlayer]: 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.
  3640. 06.06.2018 00:35:14, Marc-Antoine Ross - EOS Canada [@marcantoineross]: 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.
  3641. 06.06.2018 00:36:35, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 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
  3642. 06.06.2018 00:37:17, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Otherwise we're in an endless loop of "hey what about this?"
  3643. 06.06.2018 00:37:28, Timothy Lewis [@trustlayer]: Understood. I am now just trying to find out if anyone had tested it, or reasons they anyone may have not wanted to.
  3644. 06.06.2018 00:37:44, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Looking at the code my concern is that while it may be valid its a lot of change
  3645. 06.06.2018 00:39:04, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Considering validation tools already check every account balance i think something simpler like
  3646.  
  3647. void token::unissue(quantity){
  3648. statstable.modify( st, 0, [&]( auto& s ) {
  3649. s.supply -= quantity;
  3650. });
  3651. }
  3652.  
  3653. would be preferable in the eosio.token contract, then reconfirm balances = total supply
  3654. 06.06.2018 00:39:29, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Above is obviously invalid code, just making a point
  3655. 06.06.2018 00:40:20, Nathan Rempel | GenerEOS Sydney [@nsrempel]: That said I agree with using tools that don't require contract changes... and burning the inflation through those pre-exisisting tools, personally
  3656. .....06.06.2018 01:23:33, Emily Bush - shEOS [@emmybush]: >>invited Autumn Moss Penaloza / shEOS [@AutumnPenaloza]<<
  3657. 06.06.2018 01:33:46, Yvonne (EOShenzhen) [@yvonnekama]: great.thank you
  3658. 06.06.2018 01:42:05, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I guess its getting late in North America, but Europe is starting to wake up, looking forward to some updates soon :)
  3659. 06.06.2018 01:50:21, Luke Stokes [@lukestokes]: 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
  3660. 06.06.2018 02:24:28, Sandwich [@sandw1ch]: [[Webpage]]https://github.com/EOSIO/eos/pull/2669/files ?
  3661. 06.06.2018 02:27:31, WinLin-EOSBIXIN [@hiwinlin]: you can not find you eosiocpp?
  3662. 06.06.2018 02:28:01, WinLin-EOSBIXIN [@hiwinlin]: maybe sudo make install again
  3663. 06.06.2018 04:36:03, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Any news guys?
  3664. 06.06.2018 05:16:31, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Next call is 13:00 UTC 6th June 2018
  3665.  
  3666. I’ll post Zoom details before here.
  3667. 06.06.2018 06:21:52, Ross (EOSphere) [@rossco99]: [[Webpage]]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
  3668. 06.06.2018 07:14:16, jem [@jemxpat]: Account creation RAM costs solution
  3669.  
  3670. 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.
  3671.  
  3672. 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.
  3673.  
  3674. 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.
  3675.  
  3676. 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.
  3677.  
  3678. We believe that this simple process is the correct way to create user accounts while maintaining precise suply of total EOS tokens.
  3679. 06.06.2018 07:15:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: EVERYONE - We have our next Validation Call at 13:00 UTC
  3680.  
  3681. If you are not directly involved in testing / validation, you do not need to attend the call.
  3682.  
  3683. The focus on this call with be establishing what the current status is.
  3684.  
  3685. Agreeing what the focus is for the next 6 hours.
  3686.  
  3687. @samnoble or I will post clear minutes and actions to this group for awareness so nothing is lost in translation.
  3688. 06.06.2018 07:19:10, mao EOSREAL [@maoyifeng]: This is something super.
  3689. 06.06.2018 07:21:35, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: 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.
  3690. 06.06.2018 07:22:06, jem [@jemxpat]: 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.
  3691. .....06.06.2018 07:22:41, Laim Lais: >>unsupported service message type: messageActionChatJoinedByLink<<
  3692. .....06.06.2018 07:26:39, Sharif Bouktila - EOS Dublin [@sharifbouktila]: >>unsupported service message type: messageActionPinMessage<<
  3693. 06.06.2018 07:28:25, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 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?
  3694. 06.06.2018 07:29:46, jem [@jemxpat]: No
  3695. 06.06.2018 07:30:00, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: I am here, need to sleep sometimes =)
  3696. 06.06.2018 07:30:09, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I feel ya brother
  3697. 06.06.2018 07:30:16, Michael Yeates [@michaelyeates]: the eos in the ram and ramfee accounts is the exact amount that was spent for ram by eosio
  3698. 06.06.2018 07:31:34, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Both solutions were fine with me, please think about how we collectively make a decision and close this one out.
  3699. 06.06.2018 07:33:51, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: +1
  3700. 06.06.2018 07:35:21, David P - EOS42 [@GunnisonCap]: 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.
  3701. 06.06.2018 07:35:42, jem [@jemxpat]: It was 4 lines of script, total.
  3702. 06.06.2018 07:36:14, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 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?
  3703. 06.06.2018 07:36:25, David P - EOS42 [@GunnisonCap]: 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.
  3704. 06.06.2018 07:38:22, jem [@jemxpat]: 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.
  3705. 06.06.2018 07:38:36, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: is testnet still needed? what data use to deploy?
  3706. 06.06.2018 07:38:51, Sharif Bouktila - EOS Dublin [@sharifbouktila]: The question of which chain to launch is bigger.
  3707.  
  3708. It doesn't feel right that we are making it on what I believe is such a small issue.
  3709.  
  3710. 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.
  3711. 06.06.2018 07:40:08, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Would be nice if @bo_eossv and @dftle could provide an update, its been many hours
  3712. 06.06.2018 07:40:29, jem [@jemxpat]: No one is arguing which chain to launch. It really doesn't matter.
  3713. 06.06.2018 07:41:22, Michael Yeates [@michaelyeates]: we should reach community consensus on these issues
  3714. 06.06.2018 07:41:39, David P - EOS42 [@GunnisonCap]: 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.
  3715. 06.06.2018 07:41:55, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Can your approach be applied to B-Chain also.
  3716. 06.06.2018 07:42:30, David P - EOS42 [@GunnisonCap]: 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.
  3717. 06.06.2018 07:42:42, jem [@jemxpat]: Yes, if they made the snapshot which had been promised to GB before it was launched.
  3718. 06.06.2018 07:42:51, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Would you like to take it?
  3719. 06.06.2018 07:42:54, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I agree
  3720. 06.06.2018 07:42:55, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3721. 06.06.2018 07:43:50, Sharif Bouktila - EOS Dublin [@sharifbouktila]: So they would need a new one? Or is it possible on what they have now?? Sorry I need to get this 100% clear.
  3722. 06.06.2018 07:44:23, Michael Yeates [@michaelyeates]: they should be able to start a snapshot and fix it without rebooting
  3723. 06.06.2018 07:44:40, David P - EOS42 [@GunnisonCap]: 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
  3724. 06.06.2018 07:44:48, jem [@jemxpat]: I don't know. The snapshot had been promised, but was never delivered. I don't know if it was ever made.
  3725. 06.06.2018 07:45:01, Joshua Qiu @EOSeco [@Joshuaqiu]: can user sell initail ram?
  3726. 06.06.2018 07:45:51, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I'll do this one then. And ask for another Chair for the next one on the call.
  3727. 06.06.2018 07:46:17, David P - EOS42 [@GunnisonCap]: 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?
  3728. 06.06.2018 07:46:42, Craig Murray - EOS BlockSmith [@craigmurray100]: Dan already weighed in on this
  3729. 06.06.2018 07:46:43, David P - EOS42 [@GunnisonCap]: I think he’d probably say use the better solution if there’s no delay
  3730. 06.06.2018 07:46:49, Craig Murray - EOS BlockSmith [@craigmurray100]: there is delay
  3731. 06.06.2018 07:47:01, David P - EOS42 [@GunnisonCap]: What’s the delay?
  3732. 06.06.2018 07:47:17, Craig Murray - EOS BlockSmith [@craigmurray100]: restarting a chain, revalidating it, changing the boot sequence
  3733. 06.06.2018 07:47:34, Joshua Qiu @EOSeco [@Joshuaqiu]: i am thinking about sell inital ram, who should pay for this sell
  3734. 06.06.2018 07:48:05, David P - EOS42 [@GunnisonCap]: Thanks, I also think you’re trying to be politically neutral here too
  3735. 06.06.2018 07:48:19, David P - EOS42 [@GunnisonCap]: Is that correct @jemxpat ?
  3736. 06.06.2018 07:48:28, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: if user can sell ram, then the only thing fixed by jem’s new solution is the extra 2 or 3 EOS I think.
  3737. 06.06.2018 07:48:50, Michael Yeates [@michaelyeates]: they cannot sell their initial ram until someone else buys it
  3738. 06.06.2018 07:49:31, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: so they can, as sell means there are buyers and sellers.
  3739. 06.06.2018 07:49:52, Craig Murray - EOS BlockSmith [@craigmurray100]: i cannot believe we're still debating this non-issue
  3740. 06.06.2018 07:50:02, Michael Yeates [@michaelyeates]: if they sell too much of their initial ram then their account will not function well
  3741. 06.06.2018 07:50:04, Craig Murray - EOS BlockSmith [@craigmurray100]: even Dan knows it's not a real issue
  3742. 06.06.2018 07:50:22, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: what about I buy some more then sell it?
  3743. 06.06.2018 07:50:46, jem [@jemxpat]: Maybe Dan "knows" it. But, it is wrong, and will look very bad to some.
  3744. 06.06.2018 07:50:59, Craig Murray - EOS BlockSmith [@craigmurray100]: glad you know more than Dan
  3745. 06.06.2018 07:51:18, Craig Murray - EOS BlockSmith [@craigmurray100]: you're not even a BP, what is your stake in all this, a non BP who speaks for an entire launch group?
  3746. 06.06.2018 07:51:22, jem [@jemxpat]: I'm not a syncophant.
  3747. 06.06.2018 07:52:12, Craig Murray - EOS BlockSmith [@craigmurray100]: you think you know better than him though, clearly.
  3748. 06.06.2018 07:52:41, jem [@jemxpat]: I think he is not omniscient.
  3749. 06.06.2018 07:52:52, Craig Murray - EOS BlockSmith [@craigmurray100]: no one does
  3750. 06.06.2018 07:53:10, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: 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
  3751. 06.06.2018 07:53:52, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3752. 06.06.2018 07:54:01, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: 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.
  3753. 06.06.2018 07:54:18, jem [@jemxpat]: There is no extra 3 EOS in the chain which ran this. There was precisely 1000000000.0000 EOS.
  3754. 06.06.2018 07:55:22, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: that I agree
  3755. 06.06.2018 07:57:02, Michael Yeates [@michaelyeates]: if we dont deal with these issues yet then we will have to face them on a live running chain
  3756. 06.06.2018 07:57:56, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: so what kind of disasters we are talking about because of these 3 extra EOS?
  3757. 06.06.2018 07:58:30, jem [@jemxpat]: It is curently 19k extra.
  3758. 06.06.2018 07:58:46, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: no
  3759. 06.06.2018 07:58:50, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: user can sell ram
  3760. 06.06.2018 07:58:55, Michael Yeates [@michaelyeates]: public opinion backlash about the 20k tokens added
  3761. 06.06.2018 07:58:57, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: ram is EOS too
  3762. 06.06.2018 07:59:02, Dr Ye EOS WashingtonDC - TChain [@doc309]: what is your most recent total block count that is increasing by the second?
  3763. 06.06.2018 07:59:23, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: But this RAM issue is only an initial topic and the delta is very limited. I do not think that anybody cares..
  3764. 06.06.2018 07:59:24, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: there’s no 20K, there’s 3 EOS, user can sell ram, ram is EOS
  3765. 06.06.2018 08:00:36, Michael Yeates [@michaelyeates]: the supply discrepency is 20k
  3766. 06.06.2018 08:00:46, Sandwich [@sandw1ch]: General Information: Rounding a number after calculations, not before, can reduce accumulative dust.
  3767. 06.06.2018 08:02:34, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: we will tell public the truth. and the truth is, we give them some free ram. that’s all.
  3768. 06.06.2018 08:03:54, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: +1 .. every bank on the planet has delta in their books. It doesn't bother anyone, because it's negligible.
  3769. 06.06.2018 08:03:55, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: Just to confirm, do we have a call right now? Or in 12 hours?
  3770. 06.06.2018 08:04:21, jem [@jemxpat]: One hour later.
  3771. 06.06.2018 08:05:38, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: In 1h thank you
  3772. 06.06.2018 08:06:44, Sharif Bouktila - EOS Dublin [@sharifbouktila]: GUYS - Lets keep it on topic and professional please!
  3773. 06.06.2018 08:07:18, Dr Ye EOS WashingtonDC - TChain [@doc309]: may i ask who can turn a node to produce blocks on boot-net?
  3774. 06.06.2018 08:09:42, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: 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
  3775. 06.06.2018 08:10:37, Dr Ye EOS WashingtonDC - TChain [@doc309]: tons of things going on if you stay hands on
  3776. 06.06.2018 08:10:55, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: "net d" won't stall more than what we are already waiting
  3777. 06.06.2018 08:13:08, Dr Ye EOS WashingtonDC - TChain [@doc309]: 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)
  3778. 06.06.2018 08:14:12, Benjamin Wang | EOShenzhen [@iBenjaminWang]: EOS is not a stock. The value of EOS is based on trust and consensus.
  3779. 06.06.2018 08:14:29, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: I have a feeling Dan just wants the chain up before the hackathon 😉
  3780. 06.06.2018 08:19:32, Kyunghwan Kim - EOSeoul.io [@resvera]: [[Webpage]]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.
  3781.  
  3782. https://gist.github.com/redjade/bdbcb10708e165b29d0301c5defa1d83
  3783. 06.06.2018 08:25:10, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Longer term, a rotating chair is probably wise.
  3784. 06.06.2018 08:26:58, Dr Ye EOS WashingtonDC - TChain [@doc309]: 👍
  3785. 06.06.2018 08:27:03, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Can we try to follow a similar format, whoever curates the meeting. It seemed to be highly effective
  3786. 06.06.2018 08:31:08, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: An agenda helps
  3787. 06.06.2018 08:35:43, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: What is the status of data entry of test cases and test results?
  3788. 06.06.2018 08:36:17, David P - EOS42 [@GunnisonCap]: 😁 I think you’re right! See you in SF soon? I arrived last night.
  3789. 06.06.2018 08:37:25, David P - EOS42 [@GunnisonCap]: @sharifbouktila want a hand with some thoughts on that? I’ll DM
  3790. 06.06.2018 08:37:51, David P - EOS42 [@GunnisonCap]: Let’s just keep the call positive and productive all, we all want the same thing
  3791. 06.06.2018 08:38:26, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3792. 06.06.2018 08:38:28, Jiri Jetmar | EOS Germany | [email protected] [@jirijetmar]: 100% agree!
  3793. 06.06.2018 08:38:30, Syed Jafri | EOS Cafe / Calgary [@syed_jafri]: About to hop in a plane in 20 😁
  3794. 06.06.2018 08:43:28, David P - EOS42 [@GunnisonCap]: 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.
  3795. 06.06.2018 08:44:20, David P - EOS42 [@GunnisonCap]: 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
  3796. 06.06.2018 08:47:34, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3797. 06.06.2018 08:48:47, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 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
  3798. 06.06.2018 08:49:14, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3799. 06.06.2018 08:49:52, David P - EOS42 [@GunnisonCap]: 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
  3800. 06.06.2018 08:50:50, David P - EOS42 [@GunnisonCap]: @maoyifeng @bo_eossv Are either of you able to help get an update on this?
  3801. 06.06.2018 08:51:36, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 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
  3802. 06.06.2018 08:53:26, Sharif Bouktila - EOS Dublin [@sharifbouktila]: [[Webpage]]https://zoom.us/j/786777697
  3803. 06.06.2018 08:53:33, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Call in 7 minutes
  3804. 06.06.2018 08:56:49, mao EOSREAL [@maoyifeng]: I am still on plane. Can not join this call. Please update me your progress.
  3805. 06.06.2018 09:03:28, Hyunwoong JI - EOSeoul.io [@EOSeoul_hyunwoong]: 👍
  3806. 06.06.2018 09:11:49, Nathan Rempel | GenerEOS Sydney [@nsrempel]: @sharifbouktila on Jungle I *just* tested using my genesis account to successfully create and regproducer successfully
  3807. 06.06.2018 09:13:07, Nathan Rempel | GenerEOS Sydney [@nsrempel]: using 8kb ram, 1EOS/1EOS cpu/net
  3808. 06.06.2018 09:19:14, Brett Jeffery @ EOS the World [@EOStheWorld]: [[Webpage]]Morning meeting starting
  3809. https://zoom.us/j/786777697
  3810. 06.06.2018 09:32:27, - eoseoul.io DS Lim [@dslim]: 👍👍
  3811. 06.06.2018 09:33:42, jem [@jemxpat]: Excellent! 👍
  3812. 06.06.2018 09:35:59, Yongkil Kwon - EOSeoul.io: Awesome! 👍
  3813. 06.06.2018 09:40:41, Dr Ye EOS WashingtonDC - TChain [@doc309]: 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?
  3814. 06.06.2018 09:42:47, David Moss [@DavidMoss]: Yes, and there should be more than one.
  3815. 06.06.2018 09:43:24, Nathan Rempel | GenerEOS Sydney [@nsrempel]: mainnet in production that's not a mainnet? need to clarify the semantics there
  3816. 06.06.2018 09:44:29, Dr Ye EOS WashingtonDC - TChain [@doc309]: the boot-net for now
  3817. 06.06.2018 09:45:02, Nathan Rempel | GenerEOS Sydney [@nsrempel]: anyone can already do this... it's just a public test net
  3818. 06.06.2018 09:45:23, Nathan Rempel | GenerEOS Sydney [@nsrempel]: and should be
  3819. 06.06.2018 09:45:35, Craig Murray - EOS BlockSmith [@craigmurray100]: cryptolions has been doing this for a month or more
  3820. 06.06.2018 09:45:44, Craig Murray - EOS BlockSmith [@craigmurray100]: they are currently running latest tag
  3821. 06.06.2018 09:46:05, Dr Ye EOS WashingtonDC - TChain [@doc309]: yeah... not with real money though
  3822. 06.06.2018 09:46:15, Craig Murray - EOS BlockSmith [@craigmurray100]: you cannot run with real money and not be the mainnet
  3823. 06.06.2018 09:46:33, David Moss [@DavidMoss]: Faucets
  3824. 06.06.2018 09:46:35, Craig Murray - EOS BlockSmith [@craigmurray100]: 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"
  3825. 06.06.2018 09:46:38, David Moss [@DavidMoss]: Or sys
  3826. 06.06.2018 09:46:50, Craig Murray - EOS BlockSmith [@craigmurray100]: yes cryptolions has faucets
  3827. 06.06.2018 09:47:23, Dr Ye EOS WashingtonDC - TChain [@doc309]: we are testing on jungle with faucets
  3828. .....06.06.2018 10:00:34, Dr Ye EOS WashingtonDC - TChain [@doc309]: >>unsupported service message type: messageActionChatAddUsers<<
  3829. 06.06.2018 10:56:53, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Very productive call, thanks everyone. I'll look forward to seeing testing results appearing in the spreadsheet, lets not lose sight of that :)
  3830. 06.06.2018 10:57:50, Nathan Rempel | GenerEOS Sydney [@nsrempel]: [[Webpage]]Perhaps we can add this document to the pin to keep eyes on it: https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit?usp=sharing
  3831. 06.06.2018 10:58:57, Craig Murray - EOS BlockSmith [@craigmurray100]: that felt like a very productive meeting
  3832. 06.06.2018 10:59:02, David P - EOS42 [@GunnisonCap]: 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
  3833. 06.06.2018 10:59:44, David P - EOS42 [@GunnisonCap]: Could somebody confirm who on this channel represents them or 'EOSBschool', it seems they are not a Block Producer from an intial look
  3834. 06.06.2018 11:00:15, David P - EOS42 [@GunnisonCap]: Yes, we need to all stay focused on the issues at hand and productive resolution now.
  3835. .....06.06.2018 11:05:42, Benjamin Wang | EOShenzhen [@iBenjaminWang]: >>invited delin he [@hedelinok]<<
  3836. 06.06.2018 11:15:50, Kyunghwan Kim - EOSeoul.io [@resvera]: 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.
  3837.  
  3838. 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++.
  3839. 06.06.2018 11:16:18, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Does anyone know who in here is from the account who live-streamed that call?
  3840. 06.06.2018 11:17:19, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Else I’ll start removing people who haven’t been active in the past 48 hours in this channel and lock it
  3841. 06.06.2018 11:18:49, Mathieu Boulianne - EOS Canada [@mathieubo]: The Zoom link was shared in other public channels
  3842. 06.06.2018 11:19:05, Hubert Chang-EOSeoul.io [@hjhc00]: All I heard was someone saying 'EOSBS'? But maybe it is best to contact Mark.
  3843. 06.06.2018 11:19:56, David P - EOS42 [@GunnisonCap]: EOSBSchool - Malcolm Silberman
  3844. 06.06.2018 11:20:01, Sharif Bouktila - EOS Dublin [@sharifbouktila]: 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
  3845. 06.06.2018 11:20:03, David P - EOS42 [@GunnisonCap]: I don't know who they are on here
  3846. 06.06.2018 11:20:20, David P - EOS42 [@GunnisonCap]: They probably are on here
  3847. 06.06.2018 11:20:59, Josh Kauffman - EOS Canada [@joshkauff]: 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.
  3848. 06.06.2018 11:21:26, Sharif Bouktila - EOS Dublin [@sharifbouktila]: There was 140 today at one point
  3849. 06.06.2018 11:21:49, David P - EOS42 [@GunnisonCap]: [[Photo]]This guy
  3850. 06.06.2018 11:24:10, Hubert Chang-EOSeoul.io [@hjhc00]: Maybe our friends in US can help us out.
  3851. 06.06.2018 11:24:41, Hubert Chang-EOSeoul.io [@hjhc00]: Kevin? :) He seems to know just about everyone
  3852. 06.06.2018 11:25:44, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I don’t think they are private , but hate the idea of someone recording and streaming without consent.
  3853.  
  3854. Our position and decisions are market sensitive.
  3855. 06.06.2018 11:25:49, Brett Jeffery @ EOS the World [@EOStheWorld]: 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. 👍
  3856. 06.06.2018 11:27:19, David P - EOS42 [@GunnisonCap]: 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.
  3857. 06.06.2018 11:27:21, Sukesh Tedla (EOSGreen) [@Sukeshtedla]: +1
  3858. 06.06.2018 11:27:44, David P - EOS42 [@GunnisonCap]: Anyway let's get back to onto more important matters
  3859. 06.06.2018 11:27:58, Sukesh Tedla (EOSGreen) [@Sukeshtedla]: 👍
  3860. 06.06.2018 11:28:15, Sharif Bouktila - EOS Dublin [@sharifbouktila]: That’s fine , I don’t have the answer just yet.
  3861.  
  3862. Reminds me of my post months ago about our mantra of DBAA - “Don’t be an a**hole”
  3863. 06.06.2018 11:29:00, Ville Sundell [@SolariusFI]: So, is the consensus now, that the new selected ABP will launch their own chain?
  3864. 06.06.2018 11:29:01, David P - EOS42 [@GunnisonCap]: Somebody pin this from Sharif.. sometimes the world needs to hear the sweet tones of an Irishman telling you that
  3865. 06.06.2018 11:29:05, Brett Jeffery @ EOS the World [@EOStheWorld]: not criticizing you, just don’t want to get our team locked out just because we’re not posting much.
  3866. 06.06.2018 11:29:36, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Very good call other than that , well done all!!
  3867. 06.06.2018 11:31:23, Craig Murray - EOS BlockSmith [@craigmurray100]: no
  3868. 06.06.2018 11:32:59, Ville Sundell [@SolariusFI]: Good 😆 (Personal opinion only, I think the existing chain is good to take over by the appointed ABP)
  3869. 06.06.2018 11:46:31, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]All,
  3870.  
  3871. Thanks for another productive call!
  3872.  
  3873. PRIORITY: get that testing done! https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ
  3874.  
  3875. Find bellow the minutes, if you find anything not accurate, please suggest/comment and we will fix.
  3876. The raw log is included at the bottom of the document.
  3877.  
  3878. https://docs.google.com/document/d/17cwUuPoaH1NAYfSGgvomSvjTkDrMHdVhLaxCS5t-orQ
  3879.  
  3880. Next steps:
  3881. June 7, 0100 UTC: the next go/no go discussion, hopefully with the initial security report in hand
  3882. Meshing and ABP protection
  3883. Ben from shEOS asks: How can we insure that voting portals are handling private keys well?
  3884. More?
  3885.  
  3886.  
  3887. Thanks, good after-mor-night!
  3888. .....06.06.2018 11:46:49, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  3889. 06.06.2018 12:34:49, Denis | EOS Nation [@DenisCarriere]: 👍 thanks Cypherglass, your last video was very professional and your messaging was accurate to the current events.
  3890. 06.06.2018 12:45:49, Denis | EOS Nation [@DenisCarriere]: Amazing 💪💪 we should continue to use the same lingo P0 & P1 when presenting the security audits findings
  3891. 06.06.2018 12:47:24, Denis | EOS Nation [@DenisCarriere]: 👍 agreed, Jungle has the most experience in launching new Testnets
  3892. 06.06.2018 12:49:28, Denis | EOS Nation [@DenisCarriere]: +1 we should not be putting any labels anymore, we're all in this together
  3893. 06.06.2018 12:53:02, Denis | EOS Nation [@DenisCarriere]: 💪 we fully support your efforts! Everyone is very happy you and the other Chinese BPC'S/Community/Exchanges are pushing for this.
  3894.  
  3895. Looking forward to see these findings (good or bad) We will be more informed on our next steps moving forward after these results surface.
  3896. 06.06.2018 12:54:43, David P - EOS42 [@GunnisonCap]: 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.
  3897. 06.06.2018 12:55:11, Sharif Bouktila - EOS Dublin [@sharifbouktila]: +1
  3898. 06.06.2018 12:55:35, Mr.Z [@zlajoni]: Can't agree more!
  3899. 06.06.2018 12:57:12, Ben Sigman [@Bensig]: What will we call it?
  3900. 06.06.2018 12:58:30, Kevin Rose - EOS New York [@eosnewyork]: First few digits of the chain ID seems to make sense.
  3901. 06.06.2018 12:59:00, Craig Murray - EOS BlockSmith [@craigmurray100]: unfortuantely the chain starting in 0d6c has been forked a few times, so it's hard to refer to it just by chain id
  3902. 06.06.2018 12:59:53, Craig Murray - EOS BlockSmith [@craigmurray100]: 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.
  3903. 06.06.2018 13:00:24, Sharif Bouktila - EOS Dublin [@sharifbouktila]: A-Z , hopefully we don’t need > 26
  3904. 06.06.2018 13:00:30, David P - EOS42 [@GunnisonCap]: 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.
  3905. 06.06.2018 13:03:17, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Or how about jungle animals - a nod to the super work done there
  3906. 06.06.2018 13:03:22, Craig Murray - EOS BlockSmith [@craigmurray100]: 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?
  3907. 06.06.2018 13:04:00, Craig Murray - EOS BlockSmith [@craigmurray100]: where C D and E have the same chain ID
  3908. 06.06.2018 13:04:23, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Whatever works
  3909. 06.06.2018 13:04:28, Michael Yeates [@michaelyeates]: there are no multiple forks
  3910. 06.06.2018 13:04:42, Michael Yeates [@michaelyeates]: we have the one chain and separate private chains for testing
  3911. 06.06.2018 13:04:54, Michael Yeates [@michaelyeates]: out blocks db is available for download and testing
  3912. 06.06.2018 13:04:55, Craig Murray - EOS BlockSmith [@craigmurray100]: those are forks because they have the same ID
  3913. 06.06.2018 13:05:05, Craig Murray - EOS BlockSmith [@craigmurray100]: that's the definition of a fork
  3914. 06.06.2018 13:05:15, Craig Murray - EOS BlockSmith [@craigmurray100]: it's not derogatory, it's jsut fact
  3915. 06.06.2018 13:05:43, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3916. 06.06.2018 13:06:34, Craig Murray - EOS BlockSmith [@craigmurray100]: we're talking about a way to describe them that doesn't use these silly team names
  3917. 06.06.2018 13:06:52, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3918. 06.06.2018 13:07:19, Denis | EOS Nation [@DenisCarriere]: 👍👍 Marc is the best scribe ever!
  3919. 06.06.2018 13:08:55, Patrick B - Aloha EOS: career change? :D
  3920. 06.06.2018 13:11:29, Denis | EOS Nation [@DenisCarriere]: Agreed, I think the wording "print vs. issue" for optics the word "issuing" should be used for the global message.
  3921.  
  3922. CC: Cypherglass & EOS New York
  3923. 06.06.2018 13:12:12, Denis | EOS Nation [@DenisCarriere]: 😂 full-time scribe 📜
  3924. 06.06.2018 13:12:39, Patrick B - Aloha EOS: haha
  3925. 06.06.2018 13:13:14, Jose Toriello [@josetoriello]: +1
  3926. 06.06.2018 13:16:57, Denis | EOS Nation [@DenisCarriere]: 👎 disagree, attempting to reimplement anything that touches token balances would jeopardize the entire validation process (this is why I mentioned +2 days)
  3927.  
  3928. 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.
  3929.  
  3930. This type of change would cause a drastic delay (for what reason?)
  3931. 06.06.2018 13:19:10, Craig Murray - EOS BlockSmith [@craigmurray100]: and woudl also degrate public trust that we are making progress
  3932. 06.06.2018 13:19:53, Denis | EOS Nation [@DenisCarriere]: 🤔 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.
  3933. 06.06.2018 13:19:59, David P - EOS42 [@GunnisonCap]: 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.
  3934. .....06.06.2018 13:20:40, Alex - EOS SOCAL [@gmory]: >>invited Cesar Diaz EOSoCal [@EOSLA]<<
  3935. 06.06.2018 13:21:06, David P - EOS42 [@GunnisonCap]: 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.
  3936. 06.06.2018 13:21:23, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3937. 06.06.2018 13:21:30, Denis | EOS Nation [@DenisCarriere]: If we spin up a new chain we're at day 0 again.
  3938.  
  3939. 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
  3940. 06.06.2018 13:22:28, deck - EOS New York [@deckw]: What does that matter? The software has been tested and the validation of chain content takes 15-20 minutes
  3941. 06.06.2018 13:22:48, Timothy Lewis [@trustlayer]: +1
  3942. 06.06.2018 13:22:52, Denis | EOS Nation [@DenisCarriere]: {"initial_timestamp":"2018-06-03T13:04:31","initial_key":"EOS7m4uBgRXBM5DbXFX7FTrNiZyRzxfktmto6qQTzc2z3BhgAGHKM"}
  3943.  
  3944. June 3rd is the timestamp of 579a
  3945. 06.06.2018 13:22:59, Timothy Lewis [@trustlayer]: Why does that matter
  3946. 06.06.2018 13:23:11, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3947. 06.06.2018 13:23:31, Denis | EOS Nation [@DenisCarriere]: The software isn't changing unless we find P0 or P1
  3948. 06.06.2018 13:23:39, Timothy Lewis [@trustlayer]: Why? I’d rather a chain that is correct.
  3949. 06.06.2018 13:23:56, Timothy Lewis [@trustlayer]: “These guys can’t even get token issuance right, lol”
  3950. 06.06.2018 13:24:42, Craig Murray - EOS BlockSmith [@craigmurray100]: we're back to ram again? ugh
  3951. 06.06.2018 13:24:46, Denis | EOS Nation [@DenisCarriere]: 👎 more then running a few scripts.
  3952.  
  3953. Starting a new chain for the sake of it says "we have no confidence in the chain we've booted and validated"
  3954. 06.06.2018 13:25:57, David P - EOS42 [@GunnisonCap]: Exactly. Buddy is right I don't know why you think this takes long Denis, it doesn't.
  3955. 06.06.2018 13:26:01, Denis | EOS Nation [@DenisCarriere]: 👎 so you're against BM's decision and the majority of the BPs?
  3956. 06.06.2018 13:26:13, Timothy Lewis [@trustlayer]: 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.
  3957. 06.06.2018 13:26:26, Denis | EOS Nation [@DenisCarriere]: It's not a solution
  3958. 06.06.2018 13:26:39, Craig Murray - EOS BlockSmith [@craigmurray100]: what chain uses this solution? Is this solution coded in github? Tested?
  3959. 06.06.2018 13:26:44, Timothy Lewis [@trustlayer]: Look above at the original post.
  3960. 06.06.2018 13:26:54, Craig Murray - EOS BlockSmith [@craigmurray100]: what are the p2p addresses so i can sync to this new "proper" chain?
  3961. 06.06.2018 13:27:10, Timothy Lewis [@trustlayer]: Have a good day guys, I’m back to work.
  3962. 06.06.2018 13:27:55, Jae Chung - HKEOS [@jaechung]: How else would you run an acceptance testing chain without forking?
  3963. 06.06.2018 13:28:09, Jae Chung - HKEOS [@jaechung]: just wondering
  3964. 06.06.2018 13:28:14, David P - EOS42 [@GunnisonCap]: 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.
  3965. 06.06.2018 13:28:14, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3966. 06.06.2018 13:28:15, Denis | EOS Nation [@DenisCarriere]: Starting a new chain for the sake of it is not a good decision.
  3967.  
  3968. If you don't agree with the RAM purchase, then join another chain that has a different chain injection process.
  3969.  
  3970. Right now 579a has been validated and nothing is wrong with it
  3971. 06.06.2018 13:28:54, David P - EOS42 [@GunnisonCap]: Fair enough guys, I'm just trying to give everybody a chance here and keep us moving forwards.
  3972. 06.06.2018 13:29:13, Craig Murray - EOS BlockSmith [@craigmurray100]: a new chain is moving backwards unless we find a p0 or p1, we should not start a new chain
  3973. 06.06.2018 13:29:32, Denis | EOS Nation [@DenisCarriere]: 👍 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
  3974. 06.06.2018 13:31:30, Denis | EOS Nation [@DenisCarriere]: We are moving forward, wait for security audits from the Chinese community.
  3975.  
  3976. If no P0 / P1 problems arise, we decide after all reading the findings and call a Go/NoGo meeting (whenever that day comes)
  3977. 06.06.2018 13:31:52, Denis | EOS Nation [@DenisCarriere]: 👌
  3978. 06.06.2018 13:35:43, Denis | EOS Nation [@DenisCarriere]: This just indicates that that Chain C is a "testnet" and not a "candidate chain"
  3979.  
  3980. We've only got 1 real candidate chain by your comment
  3981. 06.06.2018 13:36:14, Craig Murray - EOS BlockSmith [@craigmurray100]: I did not suggest you would
  3982. 06.06.2018 13:36:47, Jae Chung - HKEOS [@jaechung]: 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.
  3983. 06.06.2018 13:37:38, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  3984. 06.06.2018 13:39:18, Michael Yeates [@michaelyeates]: the 1178 chain is in the hands of the community
  3985. 06.06.2018 13:39:25, Jae Chung - HKEOS [@jaechung]: ^
  3986. 06.06.2018 13:39:26, Michael Yeates [@michaelyeates]: paused and distributed
  3987. 06.06.2018 13:39:37, Jae Chung - HKEOS [@jaechung]: we have a public endpoint that we stopped with the fully synced copy at 11778
  3988. 06.06.2018 13:39:37, Craig Murray - EOS BlockSmith [@craigmurray100]: who is running the boot node for it?
  3989. 06.06.2018 13:39:48, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Real public keys from the snapshot? Or a blank testnet?
  3990. 06.06.2018 13:39:49, Michael Yeates [@michaelyeates]: its anonymous
  3991. 06.06.2018 13:40:03, Michael Yeates [@michaelyeates]: we may have just found something
  3992. 06.06.2018 13:41:01, Craig Murray - EOS BlockSmith [@craigmurray100]: what are the public endpoints for this paused chain?
  3993. .....06.06.2018 13:44:57, Peter Bue | EOSAmericas: >>invited James Davis<<
  3994. 06.06.2018 13:48:43, Jae Chung - HKEOS [@jaechung]: 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?
  3995. 06.06.2018 13:49:17, Jae Chung - HKEOS [@jaechung]: Here's a block database you can sync from, for your convenience: https://transfer.sh/OIyZl/boot-mainnet-post-resign-ramfix.tar.gz
  3996. 06.06.2018 13:49:26, Craig Murray - EOS BlockSmith [@craigmurray100]: as I said I'm having trouble with your endpoints today but if you dont want to hel that's fine
  3997. 06.06.2018 13:49:28, Craig Murray - EOS BlockSmith [@craigmurray100]: dont help
  3998. 06.06.2018 13:51:03, Jae Chung - HKEOS [@jaechung]: "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.
  3999. 06.06.2018 13:59:51, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Guys looks like @jaechung was helping, there is plenty of other channels to discuss endpoints etc..
  4000. 06.06.2018 14:01:39, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Lets try and keep in here on point. We can spin up another channel for Which Chain type discussions.
  4001.  
  4002. If I'm off topic, I'd expect someone to nudge me back into line, so please don't take offence.
  4003. 06.06.2018 14:05:22, Craig Murray - EOS BlockSmith [@craigmurray100]: 👍
  4004. 06.06.2018 14:06:18, Denis | EOS Nation [@DenisCarriere]: 👍agreed, we should keep the discussions on topic.
  4005. 06.06.2018 14:07:38, Peter Bue | EOSAmericas: 👍👍
  4006. 06.06.2018 14:20:14, Hugo Yang - EOS Silicon Valley [@hugo_eossv]: 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?
  4007. 06.06.2018 14:24:14, Denis | EOS Nation [@DenisCarriere]: That could be a discussion topic for tonight (I won't be able to attend, in a plane during call)
  4008.  
  4009. 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.
  4010.  
  4011. The filesize of these blocks is minimal, including them isn't a big deal for "launching"
  4012.  
  4013. My vote: Keep empty blocks until we launch
  4014. 06.06.2018 14:28:34, Ben Sigman [@Bensig]: 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?
  4015. 06.06.2018 14:28:34, Timothy Lewis [@trustlayer]: [[Webpage]]Updated: https://gist.github.com/redjade/bdbcb10708e165b29d0301c5defa1d83
  4016. 06.06.2018 14:31:19, Sharif Bouktila - EOS Dublin [@sharifbouktila]: 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 )
  4017.  
  4018. If I removed someone from your team, feel free to contact me directly.
  4019.  
  4020. @marcantoineross and @xebb82 are also admins , and people in here should be able to invite others.
  4021. 06.06.2018 14:36:54, deck - EOS New York [@deckw]: Thanks. Do we also want to be careful with who we share the zoom links?
  4022. 06.06.2018 14:39:59, Sharif Bouktila - EOS Dublin [@sharifbouktila]: 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.
  4023.  
  4024. Can obv put passwords but posting here is kind of the same thing.
  4025.  
  4026. I think the message sent out was probably clear enough that until we have a consensus we don't want calls streamed.
  4027. 06.06.2018 14:45:15, Rob Finch - Cypherglass.com (Block Producer) [@finchify]: Happy to do a video. Please send me any details you’d like conveyed.
  4028. 06.06.2018 14:50:58, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: 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
  4029. 06.06.2018 14:51:56, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Sounds like a good approach.
  4030. 06.06.2018 14:57:28, Kyle - EOSVibes [@TheAwakenment]: I'm also happy to do a video. Although I think this should be Steemed as an EMLG too.
  4031. 06.06.2018 14:59:22, Sharif Bouktila - EOS Dublin [@sharifbouktila]: 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.
  4032.  
  4033. Personally I don't think I could watch it back, but I know there is lots of interest.
  4034. 06.06.2018 15:03:29, Kyle - EOSVibes [@TheAwakenment]: 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!!!
  4035. 06.06.2018 15:05:36, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I hear you! - EOS FIREHOSE
  4036.  
  4037. Personally I don't think the RAM question worth going out with for now. But others might have a different opinion.
  4038. 06.06.2018 15:10:42, Jose Toriello [@josetoriello]: Yup
  4039. 06.06.2018 15:11:52, Jose Toriello [@josetoriello]: Agree. Not worth it. It will only heighten the controversy.
  4040. 06.06.2018 15:12:01, David Moss [@DavidMoss]: @igorls you here?
  4041. 06.06.2018 15:18:44, Igor Lins e Silva - EOS Rio [@igorls]: yes
  4042. 06.06.2018 15:20:24, Sharif Bouktila - EOS Dublin [@sharifbouktila]: @DavidMoss
  4043. 06.06.2018 15:21:01, Ben Sigman [@Bensig]: I just popped up this site
  4044. 06.06.2018 15:21:15, Ben Sigman [@Bensig]: [[Webpage]]https://status.producer.vote/
  4045. 06.06.2018 15:21:53, Sharif Bouktila - EOS Dublin [@sharifbouktila]: You should work in IT , nice work!
  4046. 06.06.2018 15:22:56, Sukesh Tedla (EOSGreen) [@Sukeshtedla]: This is cool. Thanks for your effort.
  4047. 06.06.2018 15:23:17, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Hopefully it will be obsolete soon , although would be a nice place for BPs to push performance stats etc...
  4048. 06.06.2018 15:24:07, Peter Sveda EOS Germany [@PeterSvedaEOSGermany]: 👍
  4049. 06.06.2018 15:24:45, Kyle - EOSVibes [@TheAwakenment]: Helpful. Thanks Ben 👍
  4050. .....06.06.2018 15:25:12, Peter Bue | EOSAmericas: >>invited Douglas Horn | EOSAmericas [@DAPPerD]<<
  4051. 06.06.2018 15:33:59, Rob Finch - Cypherglass.com (Block Producer) [@finchify]: The most important thing to convey is that the tokens are basically burned because they’re locked in the system account forever.
  4052.  
  4053. If people know that the 12k tokens are a *necessary* step in launching the chain, they will be fine with the decision.
  4054. 06.06.2018 15:35:28, Kyle - EOSVibes [@TheAwakenment]: Then is it even worth conveying?
  4055. 06.06.2018 15:47:59, Timothy Lewis [@trustlayer]: But they aren't being burned.
  4056. 06.06.2018 15:48:05, Timothy Lewis [@trustlayer]: So that's not correct information.
  4057. 06.06.2018 15:48:28, Sam - EOS Dublin [@samnoble]: 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
  4058. 06.06.2018 15:49:32, Rob Finch - Cypherglass.com (Block Producer) [@finchify]: Probably not.
  4059. 06.06.2018 15:49:38, Timothy Lewis [@trustlayer]: 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?"
  4060. 06.06.2018 15:50:03, mini - EOS Argentina [@moonxor]: We didn't reach consensus on this yesterday?
  4061. 06.06.2018 15:50:15, Timothy Lewis [@trustlayer]: That's becuase there was no fix.
  4062. 06.06.2018 15:50:53, Timothy Lewis [@trustlayer]: We are testing a fix. If it fixes, it will be brought up. If it doesn't we are comfortable launching incorrect.
  4063. 06.06.2018 15:52:52, Kyle - EOSVibes [@TheAwakenment]: 12k are being locked in the System contract forever though right? & There is no way for these EOS to ever be released right?
  4064. 06.06.2018 15:54:17, Timothy Lewis [@trustlayer]: 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.
  4065. 06.06.2018 15:54:32, Timothy Lewis [@trustlayer]: It's not a "critical" system issue by any means.
  4066. 06.06.2018 15:54:50, Timothy Lewis [@trustlayer]: It is an optical issue, in my opinion.
  4067. 06.06.2018 15:56:43, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Why not manually add inflation (4%) for Worker Proposals from when the chain was created. And use that to pay for Ram?
  4068.  
  4069. Put the rest into the WP fund. (We are going to need it)
  4070. 06.06.2018 15:57:38, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I'm also fine with the create & burn option to be clear.
  4071. 06.06.2018 15:57:47, Kyle - EOSVibes [@TheAwakenment]: 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).
  4072. 06.06.2018 15:58:18, Kyle - EOSVibes [@TheAwakenment]: Yep, send them to a null account when done.
  4073. 06.06.2018 15:58:25, Timothy Lewis [@trustlayer]: That was never on the table.
  4074. 06.06.2018 15:59:40, Timothy Lewis [@trustlayer]: 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... )
  4075. 06.06.2018 16:00:07, Timothy Lewis [@trustlayer]: Actually... Why don't you all just charge one of my accounts and we create a WP to repay me.
  4076. 06.06.2018 16:00:16, Timothy Lewis [@trustlayer]: It's like 20k tokens, right?
  4077. 06.06.2018 16:00:39, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Don't like that , but thanks for the offer. - Please vote for us 🙂
  4078. 06.06.2018 16:00:53, Timothy Lewis [@trustlayer]: I'll do anon
  4079. 06.06.2018 16:01:34, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We'll never get a WP approved for a repay. We don't even have a Worker Proposal process designed yet.
  4080. 06.06.2018 16:04:15, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Why not manually add inflation (4%) for Worker Proposals from when the chain was created. And use that to pay for Ram?
  4081. 06.06.2018 16:04:37, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Its like 100k per day
  4082. 06.06.2018 16:04:49, Kyle - EOSVibes [@TheAwakenment]: 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.
  4083. 06.06.2018 16:06:57, Timothy Lewis [@trustlayer]: I like this.
  4084. 06.06.2018 16:07:38, Timothy Lewis [@trustlayer]: maybe.
  4085. 06.06.2018 16:07:41, Timothy Lewis [@trustlayer]: let me think.
  4086. 06.06.2018 16:14:40, Kyle - EOSVibes [@TheAwakenment]: 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.
  4087. 06.06.2018 16:15:02, Timothy Lewis [@trustlayer]: +1
  4088. 06.06.2018 16:15:56, Timothy Lewis [@trustlayer]: 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.
  4089. 06.06.2018 16:16:18, Sharif Bouktila - EOS Dublin [@sharifbouktila]: +1
  4090. 06.06.2018 16:16:58, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I think we are over thinking this one.
  4091.  
  4092. Its not material , lost in the roundings after a couple of days of the chain running.
  4093. 06.06.2018 16:21:46, Kyle - EOSVibes [@TheAwakenment]: @trustlayer Yes
  4094. 06.06.2018 16:22:06, Kyle - EOSVibes [@TheAwakenment]: & Yes
  4095. 06.06.2018 16:30:27, Kevin Rose - EOS New York [@eosnewyork]: Agree. Not against @finchify making a video, he’s very good at it. But we need a “faceless” statement as well.
  4096. 06.06.2018 16:31:13, Timothy Lewis [@trustlayer]: With a mask and a voice distorter.
  4097. 06.06.2018 16:31:14, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I don't think anyone should make a video until an agreed period after official statements.
  4098. 06.06.2018 16:31:24, Timothy Lewis [@trustlayer]: +1
  4099. 06.06.2018 16:31:55, Kevin Rose - EOS New York [@eosnewyork]: I can do a mean Darth Vader.
  4100. 06.06.2018 16:47:57, Kyle - EOSVibes [@TheAwakenment]: +1
  4101. 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.
  4102. 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!
  4103. I really hope it stays like this...
  4104. 06.06.2018 16:51:20, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Really is a solid group of people, I'm more and more optimistic each day.
  4105. 06.06.2018 16:52:27, Sharif Bouktila - EOS Dublin [@sharifbouktila]: But lets stay on topic ... How is the test plans coming along 🙂
  4106. 06.06.2018 17:03:46, Ben Sigman [@Bensig]: Yes I can change it up
  4107. 06.06.2018 17:04:11, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: I’d like to see this.
  4108. 06.06.2018 17:04:42, Kevin Rose - EOS New York [@eosnewyork]: I'm better at Golem from LOTR. #tulip
  4109. 06.06.2018 17:04:44, Sam - EOS Dublin [@samnoble]: Thanks, the countdown is really helpful as time is just a blur right now 🙂
  4110. 06.06.2018 17:05:37, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: I do a mean golem myself. We
  4111. Might have to have a golem- off at Tulip.
  4112. 06.06.2018 17:06:18, Ben Sigman [@Bensig]: Proof of Vader requested by 0100
  4113. 06.06.2018 17:06:41, Ben Sigman [@Bensig]: Well, I believe that there will be a call tonight
  4114. 06.06.2018 17:06:45, Ben Sigman [@Bensig]: But not to vote
  4115. 06.06.2018 17:07:00, Branden Espinoza [@espinbrand]: I can do Chewbacca.
  4116. 06.06.2018 17:07:14, Timothy Lewis [@trustlayer]: That would be hilarious.
  4117. 06.06.2018 17:07:23, Timothy Lewis [@trustlayer]: With the electronic mask.
  4118. 06.06.2018 17:07:31, Timothy Lewis [@trustlayer]: You'd be perfect for it.
  4119. 06.06.2018 17:07:37, Timothy Lewis [@trustlayer]: (the msg)
  4120. 06.06.2018 17:07:51, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: Haha
  4121. 06.06.2018 17:09:35, Branden Espinoza [@espinbrand]: Oh geeze.
  4122. 06.06.2018 17:16:28, Branden Espinoza [@espinbrand]: I am happy to help however I can. 😁
  4123. 06.06.2018 17:22:00, Kevin Rose - EOS New York [@eosnewyork]: I’ll take “Things No One Wants” for $1,000, Alex.
  4124. 06.06.2018 17:22:17, Shaheen Counts - EOS BlockSmith [@SeanPaul19]: Hahaha
  4125. 06.06.2018 17:24:17, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Thank you @eosnewyork , see you on the other side
  4126. 06.06.2018 17:44:59, David P - EOS42 [@GunnisonCap]: Right approach 👍
  4127. 06.06.2018 17:56:33, Josh Kauffman - EOS Canada [@joshkauff]: 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.
  4128. 06.06.2018 18:06:26, Sharif Bouktila - EOS Dublin [@sharifbouktila]: The natural endpoint of all this is a dance off.
  4129.  
  4130. I trust Kev and Blue Jays to be neutral in judging.
  4131. 06.06.2018 18:08:27, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: 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?
  4132. 06.06.2018 19:58:12, Roman CryptoLions [@romanskaskiw]: zoom call coming up?
  4133. 06.06.2018 19:58:37, Nathan Rempel | GenerEOS Sydney [@nsrempel]: in one hour i think
  4134. 06.06.2018 20:01:10, Kevin Rose - EOS New York [@eosnewyork]: I should start stretching now then.
  4135. 06.06.2018 20:09:33, Marc-Antoine Ross - EOS Canada [@marcantoineross]: In one hour yes
  4136. 06.06.2018 20:16:08, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I see that eos-mainnet is 80 commits behind eosio
  4137. 06.06.2018 20:20:02, Sam - EOS Dublin [@samnoble]: [[Webpage]]@Bensig created a handy tracker for exactly that! https://status.producer.vote
  4138. .....06.06.2018 20:35:15, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>invited Celu - Blockgenic [@celur]<<
  4139. .....06.06.2018 20:35:53, Celu - Blockgenic [@celur]: >>invited Jk (Blockgenic) [@topcat2001]<<
  4140. 06.06.2018 20:41:34, Peter Bue | EOSAmericas: ^ I'd also like to confirm the call.
  4141. 06.06.2018 20:48:50, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4142. 06.06.2018 20:49:03, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Fair enough
  4143. 06.06.2018 20:50:27, Andrey Marchuk [@madz7z]: and David confirmed on the morning call that there are no critical fixes to worry about
  4144. 06.06.2018 20:57:14, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]All,
  4145.  
  4146. Here's the proposed agenda:
  4147. Security report update - Dafeng EOS Asia
  4148. ABP selection update - Kevin EOS New York
  4149. go / no go
  4150. Ben from shEOS asks: How can we insure that voting portals are handling private keys well?
  4151. Create a sub-team to prepare recommendations?
  4152.  
  4153. https://zoom.us/j/885770550
  4154. .....06.06.2018 20:57:22, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  4155. 06.06.2018 20:57:42, Timothy Lewis [@trustlayer]: Time?
  4156. 06.06.2018 20:57:50, David Moss [@DavidMoss]: 6pm
  4157. 06.06.2018 20:57:53, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Now!
  4158. 06.06.2018 20:58:14, Marc-Antoine Ross - EOS Canada [@marcantoineross]: It's always 0100UTC and 1300UTC until further notice
  4159. 06.06.2018 20:59:29, Craig Murray - EOS BlockSmith [@craigmurray100]: FOREVER!
  4160. 06.06.2018 21:00:13, Timothy Lewis [@trustlayer]: 🙂
  4161. 06.06.2018 21:08:17, Bo - EOS Silicon Valley [@bo_eossv]: [[Document, size 195'930 bytes]]
  4162. 06.06.2018 21:15:47, James Sutherland - Cypherglass.com [@JamesSutherland]: [[Document, size 719'171 bytes]]
  4163. 06.06.2018 21:17:22, Andrey Marchuk [@madz7z]: thanks
  4164. 06.06.2018 21:18:04, James Sutherland - Cypherglass.com [@JamesSutherland]: Google mangled it, but it's somewhat readable
  4165. 06.06.2018 21:18:24, Nathan Rempel | GenerEOS Sydney [@nsrempel]: the github translates pretty well
  4166. 06.06.2018 21:25:00, Devin Lee KOREOS.IO [@indend007]: Already reported by securty firm?
  4167. 06.06.2018 21:30:33, James Sutherland - Cypherglass.com [@JamesSutherland]: Preliminary, just 3 pages. More to come
  4168. 06.06.2018 21:32:09, Devin Lee KOREOS.IO [@indend007]: Thanks.
  4169. 06.06.2018 22:00:48, Craig Murray - EOS BlockSmith [@craigmurray100]: another highly productive and this time extremely effecient meeting, thanks everyone!
  4170. 06.06.2018 22:01:59, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 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
  4171. 06.06.2018 22:02:13, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Yes agreed
  4172. 06.06.2018 22:02:55, Nathan Rempel | GenerEOS Sydney [@nsrempel]: @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
  4173. 06.06.2018 22:05:22, Timothy Lewis [@trustlayer]: I'll DM you. May not fully solve the entire issue.
  4174. 06.06.2018 22:05:32, Nathan Rempel | GenerEOS Sydney [@nsrempel]: 👍
  4175. 06.06.2018 22:15:05, Tim Weston - GenerEOS (BP Sydney) [@timweston]: Hey guys, did we get a channel created to discus the voting portal etc ?
  4176. 06.06.2018 22:16:06, Tim Weston - GenerEOS (BP Sydney) [@timweston]: If not I’m happy to throw one up
  4177. 06.06.2018 22:18:44, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]All,
  4178.  
  4179. Thanks for another productive call!
  4180.  
  4181. Find bellow the minutes, if you find anything not accurate, please suggest/comment and we will fix.
  4182. The raw log is included at the bottom of the document.
  4183.  
  4184. https://docs.google.com/document/d/1HR16WF5nhNXNzkBh963ZKjSflsyBsMb0PsOhHSbQTsI
  4185.  
  4186. Next steps June 7, 1300 UTC:
  4187. Security report update - Dafeng EOS Asia
  4188. ABP selection update - Kevin EOS New York
  4189. Follow-up constitution
  4190. Review the current state of the UAT testing. Are people supplying proof of tests, adding tests, running tests
  4191. More?
  4192.  
  4193. Thanks, good after-mor-night!
  4194. .....06.06.2018 22:18:50, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  4195. 06.06.2018 22:24:17, Jk (Blockgenic) [@topcat2001]: Let me know if you do.
  4196. 06.06.2018 22:28:43, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: and the group?
  4197. 06.06.2018 22:29:00, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Tim has to up his Telegram game 🤣
  4198. 06.06.2018 22:29:41, Branden Espinoza [@espinbrand]: Tim, you ceated a channel, not a group. That is for 1 way comms only.
  4199. 06.06.2018 22:32:11, Tim Weston - GenerEOS (BP Sydney) [@timweston]: whoops will create now
  4200. 06.06.2018 22:35:24, Nathan Rempel | GenerEOS Sydney [@nsrempel]: https://t.me/joinchat/IbfNrxA6yqKbzBXSXZxteA
  4201. 06.06.2018 22:36:01, Tim Weston - GenerEOS (BP Sydney) [@timweston]: 👆🏻👆🏻 here it is guys!
  4202. 06.06.2018 23:30:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Some fun messages from @daniellarimer
  4203. 06.06.2018 23:30:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 06.06.2018 23:12:38}}
  4204. I like how serious everyone is, but perfection is enemy of good enough
  4205. 06.06.2018 23:30:27, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 06.06.2018 23:16:27}}
  4206. No, we wil run and live!
  4207. 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!!!
  4208. 06.06.2018 23:30:27, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 06.06.2018 23:19:25}}
  4209. I see people petrified by fear of unknown bugs. Life is messy. Be brave. We can overcome anything
  4210. 06.06.2018 23:30:28, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 06.06.2018 23:20:59}}
  4211. Fortune favors the bold. And voters will notice.
  4212. 06.06.2018 23:30:28, Nathan Rempel | GenerEOS Sydney [@nsrempel]: {{FWD: Daniel Larimer [@daniellarimer], 06.06.2018 23:28:17}}
  4213. 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.
  4214. 06.06.2018 23:30:53, Kyunghwan Kim - EOSeoul.io [@resvera]: Thank you! 👍
  4215. 07.06.2018 00:37:29, Ben Sigman [@Bensig]: [[Photo]]
  4216. 07.06.2018 01:20:11, Matthew Darwin - EOS Nation [@mdarwin]: Marc, thanks for the great notes!
  4217. 07.06.2018 01:38:17, Roshan - EOS Authority [@telepound]: Thanks for the notes!
  4218. 07.06.2018 03:27:23, Sandwich [@sandw1ch]: 🔥
  4219. .....07.06.2018 05:04:13, Denis | EOS Nation [@DenisCarriere]: >>invited Yves La Rose - EOS Nation [@YBNorml]<<
  4220. 07.06.2018 05:45:46, Roman CryptoLions [@romanskaskiw]: nice
  4221. 07.06.2018 08:26:08, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Next Validation Call is in 35 minutes
  4222.  
  4223.  
  4224. Security report update - Dafeng EOS Asia
  4225. ABP selection update - Kevin EOS New York
  4226. Follow-up constitution
  4227. Review the current state of the UAT testing. Are people supplying proof of tests, adding tests, running tests
  4228. More?
  4229.  
  4230. Either @marcantoineross or I will post Zoom link 5 minutes before call.
  4231. 07.06.2018 08:46:28, Tim Weston - GenerEOS (BP Sydney) [@timweston]: 👍
  4232. 07.06.2018 08:54:27, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]All,
  4233.  
  4234. Here's the proposed agenda:
  4235. Security report update - Dafeng EOS Asia
  4236. ABP selection update - Kevin EOS New York
  4237. Follow-up constitution
  4238. Review the current state of the UAT testing. Are people supplying proof of tests, adding tests, running tests
  4239. More?
  4240.  
  4241. https://zoom.us/j/438337388
  4242. .....07.06.2018 08:54:32, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  4243. 07.06.2018 08:57:03, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: Reword "Follow-up constitution" to "follow-up on Constitution Article 9 Rollback Proposal" please?
  4244. 07.06.2018 08:57:58, Marc-Antoine Ross - EOS Canada [@marcantoineross]: done in the zoom chat
  4245. .....07.06.2018 09:01:30, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>invited Miłosz Eos Emerge - Poland [@Om4tic]<<
  4246. 07.06.2018 09:03:16, Brett Jeffery @ EOS the World [@EOStheWorld]: 👍
  4247. .....07.06.2018 09:04:30, Elliot@EOS Pacific [@Elliot521]: >>invited jason wang [@Jason_wang]<<
  4248. 07.06.2018 09:16:49, Nathan Rempel | GenerEOS Sydney [@nsrempel]: [[Webpage]]https://docs.google.com/spreadsheets/d/1gJnn0KS4rgDnTowPlN80gulVI77lRgldPhH17kZOnnI
  4249. 07.06.2018 09:17:12, Nathan Rempel | GenerEOS Sydney [@nsrempel]: https://t.me/joinchat/IbfNrxA6yqKbzBXSXZxteA
  4250. 07.06.2018 09:25:12, Kyunghwan Kim - EOSeoul.io [@resvera]: [[Webpage]]Being late, but finally got tested version of contracts for adjusting 1) token supply, 2) balance of system accounts, and 3) bancor state.
  4251.  
  4252. https://github.com/eoseoul/eos-ramcost
  4253. 07.06.2018 09:31:05, Nathan Rempel | GenerEOS Sydney [@nsrempel]: looks good to me, nice and clean. we''ll need this tested in boot sequence asap (12 hours)
  4254. 07.06.2018 09:49:21, Alexandre Bourget - EOS Canada [@abourget]: 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.
  4255. 07.06.2018 09:50:29, Nathan Rempel | GenerEOS Sydney [@nsrempel]: i looked at the cpps :(
  4256. 07.06.2018 09:50:39, Nathan Rempel | GenerEOS Sydney [@nsrempel]: good catch
  4257. 07.06.2018 09:51:52, Alexandre Bourget - EOS Canada [@abourget]: That was already voted on though..
  4258. 07.06.2018 09:52:08, Nathan Rempel | GenerEOS Sydney [@nsrempel]: ok, i'll shelf it
  4259. 07.06.2018 09:56:08, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: [[Webpage]]Strongly encourage all BPs who have done testing, to log their tests here:
  4260.  
  4261. https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit#gid=1501553294
  4262. 07.06.2018 10:09:48, Kyunghwan Kim - EOSeoul.io [@resvera]: 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?
  4263. 07.06.2018 10:23:32, Ben Sigman [@Bensig]: As I understand, there were no viable alternatives. Now that there is, don’t we want to offer it to the community?
  4264. 07.06.2018 10:31:11, Kyunghwan Kim - EOSeoul.io [@resvera]: 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.
  4265. 07.06.2018 10:35:33, Alexandre Bourget - EOS Canada [@abourget]: 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.
  4266.  
  4267. I wouldn't go to war for this.
  4268. 07.06.2018 10:36:21, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Concur at this stage
  4269. 07.06.2018 10:39:06, Ren Kaidi - EOSWTZ [@FoxMr]: so， who can give a summary about what to do tomorrow?
  4270. 07.06.2018 10:39:17, Ren Kaidi - EOSWTZ [@FoxMr]: thanks
  4271. 07.06.2018 10:40:13, Kyunghwan Kim - EOSeoul.io [@resvera]: 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.
  4272. 07.06.2018 10:40:25, Nathan Rempel | GenerEOS Sydney [@nsrempel]: instructions will be available pending the result of the go / no meeting
  4273. 07.06.2018 10:40:45, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I think it's fantastic work, the timing is just difficult
  4274. 07.06.2018 10:41:08, Kyunghwan Kim - EOSeoul.io [@resvera]: I have same opinion with you. :)
  4275. 07.06.2018 10:41:23, Nathan Rempel | GenerEOS Sydney [@nsrempel]: I think anyone helping to solve issues for the launch and the community should be commended
  4276. 07.06.2018 10:41:27, Ren Kaidi - EOSWTZ [@FoxMr]: thanks
  4277. 07.06.2018 10:49:20, deck - EOS New York [@deckw]: 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?
  4278. 07.06.2018 10:49:26, deck - EOS New York [@deckw]: [[Webpage]]https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=753803902
  4279. 07.06.2018 10:52:02, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Yes
  4280. 07.06.2018 10:52:09, Nathan Rempel | GenerEOS Sydney [@nsrempel]: Fine for us
  4281. 07.06.2018 10:53:01, Nate D - Aloha EOS [@n8dee]: 👍
  4282. .....07.06.2018 11:02:34, Miłosz Eos Emerge - Poland [@Om4tic]: >>invited Krzysztof Manijak - EOSEmerge.io - Poland [@true_manner]<<
  4283. 07.06.2018 11:12:12, Timothy Lewis [@trustlayer]: Awesome. @jemxpat @jaechung
  4284. 07.06.2018 11:13:23, Timothy Lewis [@trustlayer]: This was really well done. I commend you for the effort, regardless of outcome.
  4285. 07.06.2018 11:13:54, David Moss [@DavidMoss]: +1
  4286. 07.06.2018 11:14:14, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]All,
  4287.  
  4288. Thanks for an amazing call!
  4289.  
  4290. Find bellow the minutes, if you find anything not accurate, please suggest/comment and we will fix.
  4291. The todo for next call is included in the minutes
  4292. The raw log is included at the bottom of the document.
  4293.  
  4294. https://docs.google.com/document/d/1Fpevju50lpXDH50dMH0A4NOUnUioHb7xYy76RQXG1w4
  4295.  
  4296. Next call June 8, 0100 UTC
  4297.  
  4298. Thanks, good after-mor-night!
  4299. .....07.06.2018 11:14:20, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  4300. 07.06.2018 11:14:53, David Moss [@DavidMoss]: Thanks @marcantoineross and team!
  4301. 07.06.2018 11:20:44, Jose Toriello [@josetoriello]: Someone leaked minutes...
  4302. 07.06.2018 11:20:44, Jose Toriello [@josetoriello]: {{FWD: Eduardo Cuevas, 07.06.2018 11:10:23}}
  4303. [[Webpage]]https://www.trustnodes.com/2018/06/06/eos-launch-delayed-pending-audit-results
  4304. 07.06.2018 11:23:26, Nathan Rempel | GenerEOS Sydney [@nsrempel]: neat we can reverse blocks at will
  4305. 07.06.2018 11:23:32, Nathan Rempel | GenerEOS Sydney [@nsrempel]: apparently
  4306. 07.06.2018 11:27:20, Craig Murray - EOS BlockSmith [@craigmurray100]: @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?
  4307. 07.06.2018 11:27:57, Craig Murray - EOS BlockSmith [@craigmurray100]: @DavidMoss perhaps you have comment on this as well?
  4308. 07.06.2018 11:28:22, Nathan Rempel | GenerEOS Sydney [@nsrempel]: don't think its possible for @eosnewyork to make a decision based on boot method
  4309. 07.06.2018 11:28:39, Kevin Rose - EOS New York [@eosnewyork]: 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.
  4310. 07.06.2018 11:28:40, Nathan Rempel | GenerEOS Sydney [@nsrempel]: as long as the chain is validated it could be hand bombed i think
  4311. 07.06.2018 11:28:43, Craig Murray - EOS BlockSmith [@craigmurray100]: we've argued about ram for a while now, do we even know what method one of these 16 people will use?
  4312. 07.06.2018 11:29:00, Kevin Rose - EOS New York [@eosnewyork]: I don’t think that is up to the ABP.
  4313. 07.06.2018 11:29:24, Kevin Rose - EOS New York [@eosnewyork]: Have we tested JEMs RAM option that rounds to a perfect 1BB?
  4314. 07.06.2018 11:29:37, Michael Yeates [@michaelyeates]: we have that on our chain now
  4315. 07.06.2018 11:29:46, Craig Murray - EOS BlockSmith [@craigmurray100]: what is the github link?
  4316. 07.06.2018 11:29:52, Michael Yeates [@michaelyeates]: to our chain?
  4317. 07.06.2018 11:30:02, Craig Murray - EOS BlockSmith [@craigmurray100]: to the tool used to inject it, JEM's option
  4318. 07.06.2018 11:30:14, Michael Yeates [@michaelyeates]: ill get it for you
  4319. 07.06.2018 11:30:27, Kevin Rose - EOS New York [@eosnewyork]: We have until 1600 UTC to input ABP required criteria.
  4320. 07.06.2018 11:30:46, Kevin Rose - EOS New York [@eosnewyork]: I don’t want this process to hold up a go/no-go decision at 0100
  4321. 07.06.2018 11:31:02, Jae Chung - HKEOS [@jaechung]: [[Webpage]]https://github.com/HKEOS/Ghostbusters-Testnet/tree/master/chain-validator
  4322. was sent ~3 days ago
  4323. 07.06.2018 11:31:41, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4324. 07.06.2018 11:32:27, Kevin Rose - EOS New York [@eosnewyork]: Like I said, I think that any ABP that is applying for this position is consenting to the community approved process.
  4325. 07.06.2018 11:32:43, Craig Murray - EOS BlockSmith [@craigmurray100]: then we need a community approved process pretty quick!
  4326. 07.06.2018 11:33:22, Kevin Rose - EOS New York [@eosnewyork]: 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.
  4327. 07.06.2018 11:37:04, Craig Murray - EOS BlockSmith [@craigmurray100]: 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?
  4328. 07.06.2018 11:37:36, Sheldon | EOShenzhen [@SheldonXP]: this is really awesome
  4329. 07.06.2018 11:37:40, Craig Murray - EOS BlockSmith [@craigmurray100]: I have added criteria
  4330. 07.06.2018 11:43:05, Kevin Rose - EOS New York [@eosnewyork]: If they fail I propose we go back to the list of applicants. But that’s just my opinion.
  4331. 07.06.2018 11:47:02, Craig Murray - EOS BlockSmith [@craigmurray100]: thx
  4332. 07.06.2018 11:52:32, Alex - EOS SOCAL [@gmory]: Agreed
  4333. 07.06.2018 11:53:29, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4334. 07.06.2018 11:53:58, Craig Murray - EOS BlockSmith [@craigmurray100]: i recommend we figure that out before the abp is chosen
  4335. 07.06.2018 11:55:25, Sukesh Tedla (EOSGreen) [@Sukeshtedla]: Where can one find the list of ABP candidates? I cannot find that in the document, should we add it to the doc?
  4336. 07.06.2018 11:56:14, Kevin Rose - EOS New York [@eosnewyork]: It is secret to avoid security risks and merchandizing the responsibility to the token holders.
  4337. .....07.06.2018 11:56:45, Eric_EOSARMY.io [@Eric_EOSARMY]: >>invited phajek eosarmy Patrick [@Phajek]<<
  4338. 07.06.2018 11:56:48, Kevin Rose - EOS New York [@eosnewyork]: The BPCs present on the previous 1300 UTC asked that EOS New York field and manage the list with David Moss as a witness.
  4339. .....07.06.2018 11:57:48, Miłosz Eos Emerge - Poland [@Om4tic]: >>invited Marek EOSEmerge.io - Poland [@mbaclawski]<<
  4340. 07.06.2018 11:58:11, Nate D - Aloha EOS [@n8dee]: I don't think the how matters, as long as the data state matches what everyone expects and tests pass.
  4341. 07.06.2018 11:58:38, Craig Murray - EOS BlockSmith [@craigmurray100]: so we leave it up to the abp to decide then?
  4342. 07.06.2018 11:59:22, Craig Murray - EOS BlockSmith [@craigmurray100]: we have suspended radical transparency and the list is hidden, as will be the name of the anon abp
  4343. 07.06.2018 11:59:24, Sukesh Tedla (EOSGreen) [@Sukeshtedla]: 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.
  4344. 07.06.2018 11:59:50, Nate D - Aloha EOS [@n8dee]: The process they use to boot? Yes, I think so.
  4345. 07.06.2018 12:03:09, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4346. 07.06.2018 12:04:22, Nate D - Aloha EOS [@n8dee]: 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.
  4347. 07.06.2018 12:05:01, Sukesh Tedla (EOSGreen) [@Sukeshtedla]: +1
  4348. 07.06.2018 12:05:04, Craig Murray - EOS BlockSmith [@craigmurray100]: there are 2 tools that I know of, Igor has one that uses eosjs. Alex has one that uses golang.
  4349. 07.06.2018 12:05:23, Craig Murray - EOS BlockSmith [@craigmurray100]: did we? I'm sorry I'm trying to catch up on the details i missed some of the meeting
  4350. 07.06.2018 12:05:41, Craig Murray - EOS BlockSmith [@craigmurray100]: and this method is currently expressed in Igor's repo that was linked earlier?
  4351. 07.06.2018 12:06:48, Nate D - Aloha EOS [@n8dee]: Yes, I'd have to dig up when exactly but it was 2-3 meetings ago.
  4352. 07.06.2018 12:07:29, Craig Murray - EOS BlockSmith [@craigmurray100]: 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?
  4353. 07.06.2018 12:08:13, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4354. 07.06.2018 12:08:25, Craig Murray - EOS BlockSmith [@craigmurray100]: but please if you have minutes that would be great, i would be thrilled if this was actually already resolved
  4355. 07.06.2018 12:09:18, Nate D - Aloha EOS [@n8dee]: Yeah I'm looking...
  4356. 07.06.2018 12:10:12, Nate D - Aloha EOS [@n8dee]: [[Webpage]]https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c/edit
  4357. 07.06.2018 12:12:47, Kevin Rose - EOS New York [@eosnewyork]: Can someone share the testing doc with with Dan Larimer?
  4358. 07.06.2018 12:14:02, Craig Murray - EOS BlockSmith [@craigmurray100]: [[Webpage]]https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=668547189
  4359. 07.06.2018 12:14:10, Craig Murray - EOS BlockSmith [@craigmurray100]: i've sent him that one, i think there is also another one
  4360. 07.06.2018 12:14:17, Kevin Rose - EOS New York [@eosnewyork]: Thank you
  4361. 07.06.2018 12:14:39, Craig Murray - EOS BlockSmith [@craigmurray100]: there is also Thomas's one, but i honestly haven't had time to look at it, i dont have a link handy
  4362. 07.06.2018 12:15:18, Josh Kauffman - EOS Canada [@joshkauff]: [[Webpage]]https://docs.google.com/spreadsheets/d/1dWqr9Izk4b2xJnoS94nMD0aKR6UU3Xssy7iowwtcxBQ/edit#gid=1501553294
  4363. 07.06.2018 12:15:26, Josh Kauffman - EOS Canada [@joshkauff]: ^^ Daniel
  4364. 07.06.2018 12:16:09, Josh Kauffman - EOS Canada [@joshkauff]: 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.
  4365. 07.06.2018 12:17:16, Craig Murray - EOS BlockSmith [@craigmurray100]: Ok so @jemxpat is ok with this? @jaechung and @michaelyeates and @igorls and @xebb82 and @trustlayer are all ok with this?
  4366. 07.06.2018 12:17:45, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4367. 07.06.2018 12:26:08, Michael Yeates [@michaelyeates]: please can we put this on the agenda for the next meeting
  4368. 07.06.2018 12:31:14, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]How the chain is booted does not matter as much as validation of its content.
  4369.  
  4370. We have consensus on the content of the chain, as per the minutes. Look for "Question (21:50:00)" and the notes following.
  4371. https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c
  4372. 07.06.2018 12:36:49, Craig Murray - EOS BlockSmith [@craigmurray100]: 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?
  4373. 07.06.2018 12:43:18, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Correct
  4374. 07.06.2018 12:44:14, Yves La Rose - EOS Nation [@YBNorml]: This was the consensus yesterday, yes.
  4375. 07.06.2018 12:45:27, Timothy Lewis [@trustlayer]: I like this.
  4376. 07.06.2018 12:50:15, Timothy Lewis [@trustlayer]: 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.
  4377. 07.06.2018 12:53:06, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4378. 07.06.2018 12:58:36, mini - EOS Argentina [@moonxor]: 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 :)
  4379.  
  4380. We should delay thing only for critical things. Otherwise we are in an infinite loop reaching for perfection
  4381. 07.06.2018 13:01:45, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We know how to validate the chain using a variety of tools.
  4382.  
  4383. Let @eosnewyork and @DavidMoss figure it out.
  4384.  
  4385. If that chain gets to 15% we are in business. If not we start again.
  4386. 07.06.2018 13:02:30, Denis | EOS Nation [@DenisCarriere]: {{FWD: Daniel Larimer [@daniellarimer], 07.06.2018 12:11:53}}
  4387. We are preparing a 1.0.2 update that will fix things with the optional whitelist/blacklist for contracts
  4388. 07.06.2018 13:02:42, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4389. 07.06.2018 13:03:18, Craig Murray - EOS BlockSmith [@craigmurray100]: yup, and then there's that to add to the mix 😄
  4390. 07.06.2018 13:03:50, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4391. 07.06.2018 13:07:27, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Ok - We have a process , I suggest we put it on the agenda at 01:00 UTC
  4392.  
  4393. @jemxpat @michaelyeates @trustlayer @abourget @marcantoineross
  4394.  
  4395. I propose result of next vote is set in stone.
  4396.  
  4397. Agreed?
  4398. 07.06.2018 13:08:09, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4399. 07.06.2018 13:08:30, Sharif Bouktila - EOS Dublin [@sharifbouktila]: 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
  4400. 07.06.2018 13:08:44, Jae Chung - HKEOS [@jaechung]: @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?
  4401. 07.06.2018 13:09:43, Sharif Bouktila - EOS Dublin [@sharifbouktila]: We are starting a new chain anyway aren’t we?
  4402. 07.06.2018 13:11:29, Jae Chung - HKEOS [@jaechung]: this is something important for all of us to know for mainnet— it means minimum catch up time for LIB is ~3 minutes
  4403. 07.06.2018 13:12:01, Denis | EOS Nation [@DenisCarriere]: Since we are already doing a reset on the chain, it might be something to consider.
  4404.  
  4405. I have no preference, 1.0.1 or 1.0.2 is fine with me (preference to 1.0.2 if we have concensus)
  4406. 07.06.2018 13:13:20, Jae Chung - HKEOS [@jaechung]: so you do have a preference ;)
  4407. 07.06.2018 13:13:29, Denis | EOS Nation [@DenisCarriere]: Yes, new chain is required because of constitution changes (for legal reasons)
  4408. 07.06.2018 13:13:42, Denis | EOS Nation [@DenisCarriere]: I vote 👍 for both
  4409. 07.06.2018 13:13:57, mini - EOS Argentina [@moonxor]: 21*12*2/3
  4410. 07.06.2018 13:14:26, mini - EOS Argentina [@moonxor]: @jaechung
  4411. 07.06.2018 13:14:45, Denis | EOS Nation [@DenisCarriere]: It's a patch update, no feature changes, so it shouldn't be an issue if we do or do not use it
  4412. 07.06.2018 13:15:16, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I agree we should, but don’t quite understand that as we will be able to change constitution later.
  4413. 07.06.2018 13:15:26, Denis | EOS Nation [@DenisCarriere]: Jae, do you have time to look into it? I'll support your judgement
  4414. 07.06.2018 13:16:02, Jae Chung - HKEOS [@jaechung]: yep, we're looking into it now but at the moment I agree with you— preference for 1.0.2
  4415. 07.06.2018 13:16:15, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4416. 07.06.2018 13:16:31, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Thanks
  4417. 07.06.2018 13:16:36, Denis | EOS Nation [@DenisCarriere]: We are recompiling the eosio.system ABI, this needs to be loaded in the initial boot sequence.
  4418. 07.06.2018 13:16:38, Craig Murray - EOS BlockSmith [@craigmurray100]: if we're doing a new chain, 1.0.2 yes 👍
  4419. 07.06.2018 13:17:23, Denis | EOS Nation [@DenisCarriere]: 👍 perfect
  4420. 07.06.2018 13:18:08, Jae Chung - HKEOS [@jaechung]: 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 😕
  4421. 07.06.2018 13:19:33, mini - EOS Argentina [@moonxor]: Yes shouldn't be 325, don't know if has anything to do with the boot process.
  4422. 07.06.2018 13:19:56, mini - EOS Argentina [@moonxor]: Or a bug :/
  4423. 07.06.2018 13:20:53, Craig Murray - EOS BlockSmith [@craigmurray100]: yes Dan confirmed normal operation was that, or higher
  4424. 07.06.2018 13:21:10, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: FYI, I'm still finishing off the article expressing the case for reverting Article IX. Team is reviewing now.
  4425. 07.06.2018 13:21:23, Craig Murray - EOS BlockSmith [@craigmurray100]: all the eos-bios launches stage 1 to 20 ran that way as well 300-400 lib behind head
  4426. 07.06.2018 13:24:03, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: Just want to mention that the new chain will honor unregistered users right?
  4427. 07.06.2018 13:24:31, Jae Chung - HKEOS [@jaechung]: The LIB updates in logs every time you go to the next producer, it looks something like this:
  4428. ncy: 3989 ms]
  4429. 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]
  4430. 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]
  4431. 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]
  4432. 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]
  4433. 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]
  4434. 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
  4435. ncy: 3989 ms]
  4436. 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]
  4437. 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]
  4438. 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]
  4439. 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]
  4440. 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]
  4441. 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]
  4442. 07.06.2018 13:24:44, Jae Chung - HKEOS [@jaechung]: I wouldn't be so fast to call it a problem in the boot process or a bug in the software @moonxor ;)
  4443. 07.06.2018 13:26:01, Craig Murray - EOS BlockSmith [@craigmurray100]: yes lib moves at the end of the producers turn, but still follows behind getting it's 15/21 signatures to be lib
  4444. 07.06.2018 13:26:32, mini - EOS Argentina [@moonxor]: I said I didn't know
  4445. 07.06.2018 13:26:55, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Yes
  4446. 07.06.2018 13:28:05, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: Got some holders who forget to register asking, so just want to make sure
  4447. 07.06.2018 13:28:36, Craig Murray - EOS BlockSmith [@craigmurray100]: yes 100%
  4448. 07.06.2018 13:47:36, Nate D - Aloha EOS [@n8dee]: 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?
  4449. 07.06.2018 14:11:02, Craig Murray - EOS BlockSmith [@craigmurray100]: 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
  4450. 07.06.2018 14:21:59, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: [[Webpage]]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.
  4451.  
  4452. https://forums.eosgo.io/discussion/1189/the-case-for-reverting-article-ix-9/p1?new=1
  4453. 07.06.2018 14:22:30, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: This is the write-up I promised on the 0100 call
  4454. .....07.06.2018 14:46:51, Ben Sigman [@Bensig]: >>invited Kartik Mandaville | SpringRole [@kar2905]<<
  4455. 07.06.2018 14:48:19, Ben Sigman [@Bensig]: Where is this list?
  4456. 07.06.2018 14:48:36, Josh Kauffman - EOS Canada [@joshkauff]: If you check the notes from today's call, there should be links in there
  4457. 07.06.2018 14:49:01, Josh Kauffman - EOS Canada [@joshkauff]: [[Webpage]]@Bensig https://docs.google.com/document/d/1nHEA3rfWLh4uwKmFnY9ypuRnWbOjuSy0LdKUlTapS2c
  4458. 07.06.2018 14:50:12, Ben Sigman [@Bensig]: Thank you
  4459. 07.06.2018 14:51:45, Ben Sigman [@Bensig]: Actually, I do not see any links in there for documents.
  4460. 07.06.2018 14:52:36, Josh Kauffman - EOS Canada [@joshkauff]: Shoot that's my bad, I grabbed the one from yesterday's call. One sec, gonna get the right link.
  4461. 07.06.2018 14:53:29, Josh Kauffman - EOS Canada [@joshkauff]: [[Webpage]]https://docs.google.com/spreadsheets/d/1t4p1tWs0fXf28nF2w4m5wwzO1cAknYs5XQGJLAIf1pU/edit#gid=753803902
  4462. 07.06.2018 14:53:37, Josh Kauffman - EOS Canada [@joshkauff]: that's the one that has the ABP criteria
  4463. 07.06.2018 14:55:25, Roshan - EOS Authority [@telepound]: {{FWD: Daniel Larimer [@daniellarimer], 07.06.2018 14:46:10}}
  4464. 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.
  4465. 07.06.2018 15:01:46, Sharif Bouktila - EOS Dublin [@sharifbouktila]: 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.
  4466.  
  4467. 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.
  4468. 07.06.2018 15:33:35, Timothy Lewis [@trustlayer]: Excited.
  4469. 07.06.2018 15:39:05, Jae Chung - HKEOS [@jaechung]: [[Webpage]]https://github.com/EOSIO/eos/issues/3917
  4470. 07.06.2018 15:39:14, Jae Chung - HKEOS [@jaechung]: [[Webpage]]https://github.com/EOSIO/eos/issues/3918
  4471. 07.06.2018 15:39:36, Jae Chung - HKEOS [@jaechung]: found some things while testing in the last couple of hours which we've filed
  4472. 07.06.2018 15:40:22, Jae Chung - HKEOS [@jaechung]: seems like they should be addressed soon, #3918 could be critical
  4473. 07.06.2018 15:51:20, Denis | EOS Nation [@DenisCarriere]: 👍Thanks for sharing Jae, great finds, at least using the -j flag can workaround this issue (for now until resolved)
  4474. 07.06.2018 15:56:53, Jae Chung - HKEOS [@jaechung]: yep, and I think Dan will solve #3917 with tomorrow's 1.0.2 release
  4475. 07.06.2018 15:57:30, Kyle - EOSVibes [@TheAwakenment]: Boom!💥 Good on yea Tom cat! ✅
  4476. I’m very happy to see this (apologies for the over-enthusiastic response) 😊
  4477. 07.06.2018 15:57:47, Jae Chung - HKEOS [@jaechung]: but #3918 needs attention, it could be quite dangerous
  4478. 07.06.2018 16:09:53, Denis | EOS Nation [@DenisCarriere]: 🤔I agree with Dan's comment, not too sure if that's a bug in cleos or network forks/local node environment.
  4479.  
  4480. Dan tagged it as "support" (might not be a bug)
  4481. 07.06.2018 16:17:36, Alexandre Bourget - EOS Canada [@abourget]: Yeah I remember experiencing that when some nodes were not fully sync'd ...
  4482. 07.06.2018 16:17:44, Alexandre Bourget - EOS Canada [@abourget]: it's quite surprising, though !
  4483. 07.06.2018 16:18:39, Alexandre Bourget - EOS Canada [@abourget]: We also found that, depending on network topology, setting p2p-max-nodes-per-host helps..
  4484. 07.06.2018 16:19:06, Alexandre Bourget - EOS Canada [@abourget]: we were often trying to connect many times to a node from the same office IP.. so some wouldn't be sync'd..
  4485. 07.06.2018 16:19:10, Alexandre Bourget - EOS Canada [@abourget]: but it wasn't immediately obvious
  4486. .....07.06.2018 16:37:13, Jason Wang - EOS Pacific [@jason_wang_4595]: >>unsupported service message type: messageActionChatJoinedByLink<<
  4487. .....07.06.2018 16:47:06, Dr Ye EOS WashingtonDC - TChain [@doc309]: >>unsupported service message type: messageActionChatJoinedByLink<<
  4488. 07.06.2018 16:47:59, Dr Ye EOS WashingtonDC - TChain [@doc309]: kicking .. just prevent from being kicked out again :-)
  4489. 07.06.2018 16:53:33, Dr Ye EOS WashingtonDC - TChain [@doc309]: Is 597a still the only mainnet candidate as we voted two days ago? sorry missed the latest status
  4490. 07.06.2018 17:02:47, Marc-Antoine Ross - EOS Canada [@marcantoineross]: No, there will be a new chain launched by the anonymous ABP
  4491. 07.06.2018 17:03:47, Dr Ye EOS WashingtonDC - TChain [@doc309]: ok. just let us know the new genesis and peer list
  4492. 07.06.2018 17:04:22, Jason Wang - EOS Pacific [@jason_wang_4595]: do you knwo if we have anonymous ABP selected already?
  4493. 07.06.2018 17:32:03, Timothy Lewis [@trustlayer]: Not yet
  4494. 07.06.2018 17:46:51, David P - EOS42 [@GunnisonCap]: Can ask Kevin Rose shortly he’ll be arriving at Tulip in about half an hour
  4495. 07.06.2018 17:47:16, David P - EOS42 [@GunnisonCap]: But yes not yet we’ll get an update on the call in 3hrs
  4496. 07.06.2018 20:48:53, Douglas Horn | EOSAmericas [@DAPPerD]: 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.
  4497. 07.06.2018 20:50:03, Douglas Horn | EOSAmericas [@DAPPerD]: 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.
  4498. 07.06.2018 20:54:35, Dr Ye EOS WashingtonDC - TChain [@doc309]: zoom link for the call?
  4499. 07.06.2018 20:54:49, Marc-Antoine Ross - EOS Canada [@marcantoineross]: [[Webpage]]All,
  4500.  
  4501. For internal use only for the EOS Validation (EMLG) Telegram Channel. Please do not share outside of this channel.
  4502.  
  4503. Here's the proposed agenda:
  4504.  
  4505. Re-ratify on next call the 2/3+1 for Go/NoGo
  4506. Constitution change vote + update on changes
  4507. ABP selection update
  4508. No P0 P1 reported?
  4509. Voting Portal update
  4510. Go/NoGO vote
  4511. 48 hour update + coordination of the announcements
  4512.  
  4513. https://zoom.us/j/326472166
  4514. .....07.06.2018 20:54:54, Marc-Antoine Ross - EOS Canada [@marcantoineross]: >>unsupported service message type: messageActionPinMessage<<
  4515. 07.06.2018 20:57:01, deck - EOS New York [@deckw]: 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
  4516. 07.06.2018 20:58:50, Rick Schlesinger - EOS New York [@unlockrs]: please dont forward the zoom link
  4517. 07.06.2018 21:00:21, Douglas Horn | EOSAmericas [@DAPPerD]: 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.
  4518. 07.06.2018 21:01:05, Douglas Horn | EOSAmericas [@DAPPerD]: We're not forwarding it. It's to our team member.
  4519. 07.06.2018 21:01:19, Rohan - EOSauthority [@RohanWillAnswer]: Ok
  4520. 07.06.2018 21:01:42, Rick Schlesinger - EOS New York [@unlockrs]: im saying dont forward it to public channels. you can provide to your team members of course.
  4521. 07.06.2018 21:02:00, Rohan - EOSauthority [@RohanWillAnswer]: Is the link out yet?
  4522. 07.06.2018 21:02:06, Douglas Horn | EOSAmericas [@DAPPerD]: 👍
  4523. 07.06.2018 21:02:09, Rohan - EOSauthority [@RohanWillAnswer]: Can’t find it anywhere?
  4524. 07.06.2018 21:02:16, Rick Schlesinger - EOS New York [@unlockrs]: scroll up about 7 lines
  4525. 07.06.2018 21:21:09, Rohan - EOSauthority [@RohanWillAnswer]: I think it’s my 2AM brain. Thanks.
  4526. 07.06.2018 22:00:03, Alexandre Bourget - EOS Canada [@abourget]: @daniellarimer hey Dan, what would be the impact of transfering all EOS out the eosio.ram and eosio.ramfee accounts, before eosio resignation ?
  4527. 07.06.2018 22:00:38, Daniel Larimer [@daniellarimer]: Ram is used by market maker
  4528. 07.06.2018 22:01:08, Daniel Larimer [@daniellarimer]: Ramfee is at community disposal
  4529. 07.06.2018 22:01:13, Roman CryptoLions [@romanskaskiw]: @jemxpat
  4530. 07.06.2018 22:01:59, jem [@jemxpat]: No user "gifted" with ram would be able to sell until some other user buys new ram post 15% activation. Tested.
  4531. 07.06.2018 22:05:46, Daniel Larimer [@daniellarimer]: It violates bancor algorithm invariant
  4532. 07.06.2018 22:06:01, Kyunghwan Kim - EOSeoul.io [@resvera]: 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.
  4533.  
  4534. and transfer of token doesn’t impact the supply of token, also.
  4535. 07.06.2018 22:06:30, jem [@jemxpat]: KHKim is correct. There is no violation of Bancor with this method.
  4536. 07.06.2018 22:06:52, Daniel Larimer [@daniellarimer]: It prevents market maker from filling orders
  4537. 07.06.2018 22:07:11, jem [@jemxpat]: Only until new user buys ram.
  4538. 07.06.2018 22:09:03, David Moss [@DavidMoss]: [[Webpage]]Dan, we need a comment on https://github.com/EOSIO/eos/issues/3918
  4539. .....07.06.2018 22:11:25, Marshall - SaltBlock [@marshallslc]: >>invited Robrigo - EOS Detroit [@robrigo]<<
  4540. 07.06.2018 22:17:12, Robrigo - EOS Detroit [@robrigo]: Thanks for the add @marshallslc.
  4541. 07.06.2018 22:17:27, Marshall - SaltBlock [@marshallslc]: You're welcome
  4542. 07.06.2018 22:26:28, Andrey Marchuk [@madz7z]: Tulip conf cannot join back because of 200 participants limits
  4543. 07.06.2018 22:29:15, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: TRY AGAIN in a few minutes
  4544. 07.06.2018 22:46:14, Ben Sigman [@Bensig]: [[Webpage]]https://docs.google.com/spreadsheets/d/1gJnn0KS4rgDnTowPlN80gulVI77lRgldPhH17kZOnnI/edit#gid=744644035
  4545. 07.06.2018 22:57:26, Alexandre Bourget - EOS Canada [@abourget]: @daniellarimer do you think it makes sense to create an eosio.burned account, where we can put things in ?
  4546. 07.06.2018 22:57:35, Alexandre Bourget - EOS Canada [@abourget]: If you're planning a recall action, maybe it's useless..
  4547. 07.06.2018 23:04:21, Chitty 🅑 - EOS Argentina [@JChitty]: Is phill from eos switzerland here?.. I am just wondering if they are a bp since I havent seen them before
  4548. 07.06.2018 23:07:09, Jose Toriello [@josetoriello]: Good question
  4549. 07.06.2018 23:12:18, Heejae - EOSYS.io [@heejaejoo]: Me too.
  4550. 07.06.2018 23:13:44, Chitty 🅑 - EOS Argentina [@JChitty]: I think there are a couple of fake bps in the chat
  4551. 07.06.2018 23:15:28, Igor Lins e Silva - EOS Rio [@igorls]: 👍
  4552. 07.06.2018 23:15:47, Rick Schlesinger - EOS New York [@unlockrs]: do the vote here?
  4553. 07.06.2018 23:16:10, J.T. - EOS the World [@HartParr]: Yes.
  4554. 07.06.2018 23:16:21, J.T. - EOS the World [@HartParr]: Or post a new straw poll here.
  4555. .....07.06.2018 23:17:20, An Byung Chan - EOSYS [@Anbyungchan]: >>invited Lievin Kim - EOSYS [@lievin_kim]<<
  4556. 07.06.2018 23:18:11, David P - EOS42 [@GunnisonCap]: I think Phil from EOS Switzerland is a fake. Never once heard of them on any channel.
  4557. .....07.06.2018 23:18:15, Ricardo Marlière - EOS Brazil [@rbmarliere]: >>invited EOS - Antarctica [@jsw513]<<
  4558. 07.06.2018 23:18:32, Ross (EOSphere) [@rossco99]: Was thinking the same
  4559. 07.06.2018 23:18:34, mini - EOS Argentina [@moonxor]: Me neither
  4560. 07.06.2018 23:18:43, Chitty 🅑 - EOS Argentina [@JChitty]: he is fake, and looks like a troll
  4561. 07.06.2018 23:18:44, J.T. - EOS the World [@HartParr]: agreed.
  4562. 07.06.2018 23:18:50, Pascal Van Wy | EOS Network by Advanced Blockchain AG [@vanwy]: agreed
  4563. 07.06.2018 23:18:53, Patrick B - Aloha EOS: He's definitely trolling
  4564. 07.06.2018 23:19:19, Rohan - EOSauthority [@RohanWillAnswer]: Good find..
  4565. 07.06.2018 23:19:20, Rick Schlesinger - EOS New York [@unlockrs]: +1
  4566. 07.06.2018 23:19:38, Alex - EOS SOCAL [@gmory]: +1
  4567. 07.06.2018 23:20:09, Hubert Chang-EOSeoul.io [@hjhc00]: Can we kick him out from the call?
  4568. 07.06.2018 23:20:11, Jacky - JEDA [@newbdez33]: +1
  4569. 07.06.2018 23:20:11, Jacky - JEDA [@newbdez33]: +1
  4570. 07.06.2018 23:20:11, Jacky - JEDA [@newbdez33]: +1
  4571. 07.06.2018 23:20:14, David P - EOS42 [@GunnisonCap]: Yes please
  4572. 07.06.2018 23:20:28, David P - EOS42 [@GunnisonCap]: And various others who are clear no’s
  4573. 07.06.2018 23:20:37, Khosi Morafo eosAfrica [@khosimorafo]: +1
  4574. 07.06.2018 23:20:37, Denis | EOS Nation [@DenisCarriere]: +1 for ELMG voting
  4575. 07.06.2018 23:20:47, Andrey Marchuk [@madz7z]: +1
  4576. 07.06.2018 23:20:57, Kevin Rose - EOS New York [@eosnewyork]: +1
  4577. 07.06.2018 23:21:01, Craig Murray - EOS BlockSmith [@craigmurray100]: +1
  4578. .....07.06.2018 23:21:03, Ben Sigman [@Bensig]: >>invited Kurt Braget | White Rabbit ICOs [@kurtybot]<<
  4579. 07.06.2018 23:21:05, Bean@EOS Cannon [@Luckybean]: +1
  4580. 07.06.2018 23:21:14, Pascal Van Wy | EOS Network by Advanced Blockchain AG [@vanwy]: +1
  4581. .....07.06.2018 23:21:23, jem [@jemxpat]: >>invited Nicholas Mullesch EOS.Fish [@BitcoinRootUser]<<
  4582. 07.06.2018 23:21:39, Cryptosufi - 威杰 - BitSpace [@KryptoSufi]: +1
  4583. 07.06.2018 23:21:41, Eric - sw/eden [@xebb82]: Can we postpone the vote until 13:00 and have some tool ready?
  4584. 07.06.2018 23:21:43, Nicholas Mullesch EOS.Fish [@BitcoinRootUser]: Thank you Jem!
  4585. 07.06.2018 23:22:09, Denis | EOS Nation [@DenisCarriere]: 👎
  4586. 07.06.2018 23:22:09, Issay@OracleChain [@issayTseng]: +1
  4587. 07.06.2018 23:23:17, Douglas Horn | EOSAmericas [@DAPPerD]: 👎
  4588. 07.06.2018 23:23:39, Nicholas Mullesch EOS.Fish [@BitcoinRootUser]: +1
  4589. 07.06.2018 23:23:40, Chitty 🅑 - EOS Argentina [@JChitty]: we have most bps online now, lets vote
  4590. 07.06.2018 23:23:47, Cryptosufi - 威杰 - BitSpace [@KryptoSufi]: We could start cleos voting, until audited tools arrive.
  4591. 07.06.2018 23:23:57, Eric - sw/eden [@xebb82]: I'm up for whatever, this just feels like a farce...
  4592. 07.06.2018 23:24:03, Rohan - EOSauthority [@RohanWillAnswer]: Please stop posting messages.. wait for Sharif’s question and then vote..
  4593. 07.06.2018 23:24:21, Josh Kauffman - EOS Canada [@joshkauff]: -----------------------------------------------------------------------------------------------------------------------------
  4594. PLEASE DO NOT WRITE ANYTHING BELOW THIS UNTIL THOMAS HAS POSTED THE QUESTION IN THIS CHANNEL
  4595. -----------------------------------------------------------------------------------------------------------------------------
  4596. 07.06.2018 23:24:37, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: [Sharif will post the question]
  4597. 07.06.2018 23:24:59, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: You need permission
  4598. This form can only be viewed by users in the owner's organization.
  4599. 07.06.2018 23:25:13, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Please confirm using GO/ NO GO to launch at 13:00 UTC 8th June 2018 using current release.
  4600. 07.06.2018 23:25:16, Denis | EOS Nation [@DenisCarriere]: No need for form
  4601. 07.06.2018 23:25:20, Cryptosufi - 威杰 - BitSpace [@KryptoSufi]: Go
  4602. 07.06.2018 23:25:26, Sebastian Castro - EOS Argentina 🇦🇷 [@sebicas]: Go
  4603. 07.06.2018 23:25:30, Ralf Weinand | GenerEOS (BP Sydney) [@RalfWei]: Go
  4604. 07.06.2018 23:25:30, James Sutherland - Cypherglass.com [@JamesSutherland]: Go
  4605. 07.06.2018 23:25:31, Rohan - EOSauthority [@RohanWillAnswer]: Go - EOS Authority
  4606. 07.06.2018 23:25:31, Alex - EOS SOCAL [@gmory]: Go
  4607. 07.06.2018 23:25:32, Nate D - Aloha EOS [@n8dee]: GO
  4608. 07.06.2018 23:25:33, Marek EOSEmerge.io - Poland [@mbaclawski]: GO
  4609. 07.06.2018 23:25:34, Domi - EOS Rio [@domiscd]: the abp wasn't even selected, poor him if it's a go
  4610. 07.06.2018 23:25:34, EOS - Antarctica [@jsw513]: No go.
  4611. 07.06.2018 23:25:34, zhangzc | Onechain [@zhangzc]: GO
  4612. 07.06.2018 23:25:34, Jose Toriello [@josetoriello]: Go
  4613. 07.06.2018 23:25:38, Craig Murray - EOS BlockSmith [@craigmurray100]: go
  4614. 07.06.2018 23:25:40, Andrey Marchuk [@madz7z]: Go - BlockEOS.io
  4615. 07.06.2018 23:25:40, Jorge Ferrando - EOSMetal [@jorfermo]: Go
  4616. 07.06.2018 23:25:40, Denis | EOS Nation [@DenisCarriere]: GO
  4617. 07.06.2018 23:25:40, Ross (EOSphere) [@rossco99]: Go
  4618. 07.06.2018 23:25:40, [email protected] [@crazybits]: Go Go Go
  4619. 07.06.2018 23:25:40, Marshall - SaltBlock [@marshallslc]: Go
  4620. 07.06.2018 23:25:42, deck - EOS New York [@deckw]: go
  4621. 07.06.2018 23:25:43, Kedar Iyer | LibertyBlock [@k26dr]: GO
  4622. 07.06.2018 23:25:43, Nicholas Mullesch EOS.Fish [@BitcoinRootUser]: Go
  4623. 07.06.2018 23:25:43, Joshua Qiu @EOSeco [@Joshuaqiu]: Go
  4624. 07.06.2018 23:25:44, Robert DeWilder - Worbli [@BrownDonahue]: go
  4625. 07.06.2018 23:25:45, Miłosz Eos Emerge - Poland [@Om4tic]: Go
  4626. 07.06.2018 23:25:49, Sharif Bouktila - EOS Dublin [@sharifbouktila]: No Go
  4627. 07.06.2018 23:25:54, Eric - sw/eden [@xebb82]: No Go
  4628. 07.06.2018 23:25:56, Jason Wang - EOS Pacific [@jason_wang_4595]: Go
  4629. 07.06.2018 23:25:57, Jialin Li - EOS WTZ [@Jialinli]: Go
  4630. 07.06.2018 23:25:58, jem [@jemxpat]: jem proxy BP2 EOSPH hkeos eoskh Shenzhen Acro Tribes eosviet
  4631. No Go
  4632. 07.06.2018 23:26:02, Hugo Yang - EOS Silicon Valley [@hugo_eossv]: No go
  4633. 07.06.2018 23:26:03, Timothy Lewis [@trustlayer]: No go
  4634. 07.06.2018 23:26:04, Issay@OracleChain [@issayTseng]: NO GO
  4635. 07.06.2018 23:26:07, Igor Lins e Silva - EOS Rio [@igorls]: No go
  4636. 07.06.2018 23:26:09, Basit Raza - EOSVibes [@boltxyz]: GO
  4637. 07.06.2018 23:26:12, Marc-Antoine Ross - EOS Canada [@marcantoineross]: Go
  4638. 07.06.2018 23:26:12, ndoy |EOS Cafe: Calgary | [@n_doy]: GO
  4639. 07.06.2018 23:26:13, Ian(Yahuang Wu) - MEET.ONE [@wuyahuang]: NO GO.
  4640. 07.06.2018 23:26:13, Pete BlockMatrix [@blockmatrixpete]: no go
  4641. 07.06.2018 23:26:14, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: GO
  4642. 07.06.2018 23:26:17, Ricardo Marlière - EOS Brazil [@rbmarliere]: no go... why the rush? 1.0.2 is not even out
  4643. 07.06.2018 23:26:18, Jacky - JEDA [@newbdez33]: GO
  4644. 07.06.2018 23:26:18, Celu - Blockgenic [@celur]: Go
  4645. 07.06.2018 23:26:20, zhangzc | Onechain [@zhangzc]: GO
  4646. 07.06.2018 23:26:22, J.T. - EOS the World [@HartParr]: No Go.
  4647. 07.06.2018 23:26:22, Ravi (Blockpro.one) [@ravincal]: No Go
  4648. 07.06.2018 23:26:27, Gordo | HelloEOS [@gordoor]: go
  4649. 07.06.2018 23:26:29, [email protected] [@qianxiaofeng]: no go
  4650. 07.06.2018 23:26:35, Robin [email protected] [@robinwen]: Go
  4651. 07.06.2018 23:26:37, Dafeng Guo - EOS Asia [@dftle]: Go
  4652. 07.06.2018 23:26:43, WinLin-EOSBIXIN [@hiwinlin]: GO
  4653. 07.06.2018 23:26:44, Ben Sigman [@Bensig]: No Go
  4654. 07.06.2018 23:26:46, David P - EOS42 [@GunnisonCap]: No go
  4655. 07.06.2018 23:26:49, Emily Bush - shEOS [@emmybush]: No go
  4656. 07.06.2018 23:26:49, Pascal Van Wy | EOS Network by Advanced Blockchain AG [@vanwy]: No Go
  4657. 07.06.2018 23:27:00, Heejae - EOSYS.io [@heejaejoo]: GO
  4658. 07.06.2018 23:27:09, Guillaume @eostitan.com [@gyom_eos_titan]: No go
  4659. 07.06.2018 23:27:12, heipacker eosunion [@heipacker]: go
  4660. 07.06.2018 23:27:16, Hubert Chang-EOSeoul.io [@hjhc00]: No go
  4661. 07.06.2018 23:27:22, Bohdan CryptoLions 🦁 [@BohdanCryptoLions]: no go
  4662. 07.06.2018 23:27:22, Luis Fernando G : EOSMESOdotio 🇬🇹 [@Maski_LF]: No go
  4663. 07.06.2018 23:27:28, Yvonne (EOShenzhen) [@yvonnekama]: no go
  4664. 07.06.2018 23:27:45, Zhao Yu@ EOSLaoMao.com [@zhaoyu]: duplicate
  4665. 07.06.2018 23:27:58, Robrigo - EOS Detroit [@robrigo]: no go
  4666. 07.06.2018 23:28:04, Douglas Horn | EOSAmericas [@DAPPerD]: No go
  4667. 07.06.2018 23:29:20, phajek eosarmy Patrick [@Phajek]: no go
  4668. .....07.06.2018 23:30:13, Robrigo - EOS Detroit [@robrigo]: >>invited jesta — Greymass [@jestagram]<<
  4669. 07.06.2018 23:30:44, jesta — Greymass [@jestagram]: go
  4670. 07.06.2018 23:31:26, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: END OF VOTING END OF VOTING END OF VOTING
  4671. 07.06.2018 23:31:32, Jose Toriello [@josetoriello]: (Eosmeso 1 vote is no go. Sorry for confusion)
  4672. 07.06.2018 23:32:11, Mathieu Boulianne - EOS Canada [@mathieubo]: On another note, on the Print / Work Out vote, I got (after cleaning the data):
  4673. -55 Print
  4674. -31 work out
  4675. 07.06.2018 23:33:20, jem [@jemxpat]: Appoint ABP, let hiim get ready.
  4676. 07.06.2018 23:33:25, Denis | EOS Nation [@DenisCarriere]: I believe the "no go" is about the RAM disagreement
  4677. 07.06.2018 23:33:25, Timothy Lewis [@trustlayer]: There is a lot of deleting going on in this channel
  4678. 07.06.2018 23:33:36, Jose Toriello [@josetoriello]: Reason was no clarity on print/ram issue
  4679. 07.06.2018 23:33:53, Craig Murray - EOS BlockSmith [@craigmurray100]: dan was very clear we should not take the RAM balance
  4680. 07.06.2018 23:34:01, Craig Murray - EOS BlockSmith [@craigmurray100]: Dan said there is only 1 good option, print
  4681. 07.06.2018 23:34:02, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I've deleted some comments in the voting window
  4682. 07.06.2018 23:34:11, Sebastian Castro - EOS Argentina 🇦🇷 [@sebicas]: +1
  4683. 07.06.2018 23:34:16, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Only Me , Marc and Eric are admins
  4684. 07.06.2018 23:34:17, Robrigo - EOS Detroit [@robrigo]: My specific reason is waiting to launch with v1.0.2 tag. Would vote GO after tomorrow.
  4685. 07.06.2018 23:34:25, Timothy Lewis [@trustlayer]: Same
  4686. 07.06.2018 23:34:26, Jose Toriello [@josetoriello]: I know. But the vote was not counted
  4687. 07.06.2018 23:34:32, Craig Murray - EOS BlockSmith [@craigmurray100]: why not wait to 1.0.3? or 1.1? or 2.0?
  4688. 07.06.2018 23:34:42, Craig Murray - EOS BlockSmith [@craigmurray100]: no major issues fixed in 1.0.2
  4689. 07.06.2018 23:34:52, Robrigo - EOS Detroit [@robrigo]: Because 1.0.3 is 8 days away, not 1 day away
  4690. 07.06.2018 23:35:03, jesta — Greymass [@jestagram]: You wouldn't even have to upgrade to 1.0.2 immediately.
  4691. 07.06.2018 23:35:13, Robrigo - EOS Detroit [@robrigo]: You asked, I answered :)
  4692. 07.06.2018 23:35:17, Timothy Lewis [@trustlayer]: We also will likely get an opinion from Dan on the lost transaction issue.
  4693. 07.06.2018 23:35:41, Sherman EOSREAL [@ShermanXie]: go
  4694. 07.06.2018 23:35:42, Timothy Lewis [@trustlayer]: Get ABP selected
  4695. 07.06.2018 23:35:46, Issay@OracleChain [@issayTseng]: we thought the 3918 issue might be P1, so wait for 1.0.2
  4696. 07.06.2018 23:35:48, Timothy Lewis [@trustlayer]: Have them prepare
  4697. 07.06.2018 23:36:18, EOS - Antarctica [@jsw513]: The reasoning for someone’s vote is irrelevant. We took a vote. Use the numbers.
  4698. 07.06.2018 23:36:23, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: I'm counting 39 GO to 25 NO GO in the telegram channel
  4699. 07.06.2018 23:37:00, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: I can't promise that the data is completely clean
  4700. 07.06.2018 23:37:13, Ravi (Blockpro.one) [@ravincal]: Many BP missing here because not everyone here
  4701. 07.06.2018 23:37:15, EOS - Antarctica [@jsw513]: One does not get to the chance to try and sway opinion after the election.
  4702. .....07.06.2018 23:37:24, Ben Sigman [@Bensig]: >>invited Tal Muskal | LiquidEOS [@tmuskal]<<
  4703. 07.06.2018 23:37:36, Denis | EOS Nation [@DenisCarriere]: 👎 1.0.2 is not a show stopper
  4704. 07.06.2018 23:37:43, Jose Toriello [@josetoriello]: +1
  4705. 07.06.2018 23:37:46, Issay@OracleChain [@issayTseng]: but another reason is not all BPs is present here
  4706. 07.06.2018 23:37:53, Alexandre Bourget - EOS Canada [@abourget]: https://abourget.keybase.pub/votetallysum.txt
  4707. 07.06.2018 23:37:55, Jacky - JEDA [@newbdez33]: is 1.0.2 fixes any P0 or P1 issue?
  4708. 07.06.2018 23:37:57, Alexandre Bourget - EOS Canada [@abourget]: That's my data ^^
  4709. 07.06.2018 23:38:23, Nate D - Aloha EOS [@n8dee]: No
  4710. 07.06.2018 23:38:27, Domi - EOS Rio [@domiscd]: 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
  4711. 07.06.2018 23:38:27, Craig Murray - EOS BlockSmith [@craigmurray100]: no
  4712. 07.06.2018 23:38:30, James Sutherland - Cypherglass.com [@JamesSutherland]: 👍
  4713. 07.06.2018 23:39:42, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: The first vote was 52 to 21 // a 71% YES
  4714. 07.06.2018 23:39:45, heipacker eosunion [@heipacker]: go
  4715. 07.06.2018 23:40:02, Jacky - JEDA [@newbdez33]: then there is no reason we have to wait for 1.0.2 for my understanding.
  4716. 07.06.2018 23:40:18, EOS - Antarctica [@jsw513]: Why are we taking a vote, if we're not going to put the results into place?
  4717. 07.06.2018 23:40:25, Alex - EOS SOCAL [@gmory]: 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.
  4718. 07.06.2018 23:43:42, Alex - EOS SOCAL [@gmory]: But also regarding that, the schedule was announced long ago. The abp knew this 12 hour slot was a potential go time.
  4719. 07.06.2018 23:43:47, Alex - EOS SOCAL [@gmory]: Regardless of timezone
  4720. 07.06.2018 23:44:29, Issay@OracleChain [@issayTseng]: [[Photo]]
  4721. .....07.06.2018 23:45:05, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: >>invited Li Peng | ChainPool [@EOSMalaysia]<<
  4722. 07.06.2018 23:45:48, Li Peng | ChainPool [@EOSMalaysia](you): Thanks
  4723. 07.06.2018 23:46:17, ndoy |EOS Cafe: Calgary | [@n_doy]: this might be fake:
  4724. From deadlock - EOSIO.SG to Everyone: 09:44 PM
  4725. why celeb has EOSIO.SG website under the name
  4726. 07.06.2018 23:46:41, ndoy |EOS Cafe: Calgary | [@n_doy]: deadlock doesn't know him
  4727. 07.06.2018 23:46:49, Li Peng | ChainPool [@EOSMalaysia](you): Sorry, there's been some confusion
  4728. 07.06.2018 23:46:51, Li Peng | ChainPool [@EOSMalaysia](you): One second
  4729. 07.06.2018 23:48:37, Denis | EOS Nation [@DenisCarriere]: No go's should provide reasons (not blank no go's)
  4730. 07.06.2018 23:48:54, EOS - Antarctica [@jsw513]: Why? A vote is a vote
  4731. 07.06.2018 23:49:07, Lee - EOSTEA [@strahe]: go
  4732. 07.06.2018 23:49:55, Jose Toriello [@josetoriello]: 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.
  4733.  
  4734. Then we are changing from no go to GO
  4735. .....07.06.2018 23:50:11, An Byung Chan - EOSYS [@Anbyungchan]: >>invited Ashley Gan<<
  4736. 07.06.2018 23:50:54, Denis | EOS Nation [@DenisCarriere]: Can't update to 1.0.2, code is not released (maybe released)
  4737. 07.06.2018 23:50:59, Marek EOSEmerge.io - Poland [@mbaclawski]: too bad that it didn't happen today
  4738. 07.06.2018 23:51:17, Marek EOSEmerge.io - Poland [@mbaclawski]: Its a real pitty that they can't make a good reason for no go
  4739. 07.06.2018 23:51:50, zhangzc | Onechain [@zhangzc]: +1
  4740. 07.06.2018 23:53:20, Denis | EOS Nation [@DenisCarriere]: How many hours for validation + meshes (12 hours?)
  4741. 07.06.2018 23:53:44, jem [@jemxpat]: Yes, when you don't like the vote, be sure to challenge the motivation and reason of the opposition. What a great strategy!
  4742. 07.06.2018 23:54:39, Daniel Larimer [@daniellarimer]: conclusion?
  4743. 07.06.2018 23:55:02, jem [@jemxpat]: No conclusion yet, still herding cats.
  4744. 07.06.2018 23:55:14, Craig Murray - EOS BlockSmith [@craigmurray100]: too many people are no-go, so it's no go..
  4745. 07.06.2018 23:55:20, Daniel Larimer [@daniellarimer]: would these be crypto-kitties
  4746. 07.06.2018 23:55:25, Rick Schlesinger - EOS New York [@unlockrs]: its a no-go
  4747. 07.06.2018 23:55:30, jem [@jemxpat]: Exactly!, Herding crypto kitties!
  4748. 07.06.2018 23:55:35, Roman CryptoLions [@romanskaskiw]: It'll happen next vote.
  4749. 07.06.2018 23:55:46, David P - EOS42 [@GunnisonCap]: Yes, I think so next vote
  4750. .....07.06.2018 23:55:47, Pascal Van Wy | EOS Network by Advanced Blockchain AG [@vanwy]: >>invited Pascal | EOS Network by Advanced Blockchain AG [@maplefrog]<<
  4751. 07.06.2018 23:55:59, Domi - EOS Rio [@domiscd]: yes, next will be go for sure ☺
  4752. 07.06.2018 23:56:05, Rick Schlesinger - EOS New York [@unlockrs]: +1
  4753. 07.06.2018 23:56:11, jem [@jemxpat]: I think so.
  4754. 07.06.2018 23:56:22, Roman CryptoLions [@romanskaskiw]: See you all in 9 hrs.
  4755. 07.06.2018 23:56:27, Roman CryptoLions [@romanskaskiw]: 7 am here. 😊
  4756. 07.06.2018 23:56:27, Pete BlockMatrix [@blockmatrixpete]: 👍
  4757. 07.06.2018 23:56:32, Lars Ihler - BitSpace [@LarsIhler]: 06 am
  4758. 07.06.2018 23:56:47, Igor Lins e Silva - EOS Rio [@igorls]: why not use the top_eos_bps_test team on keybase?, the one that Thomas set up for disaster recovery
  4759. 07.06.2018 23:57:21, Igor Lins e Silva - EOS Rio [@igorls]: it far more verifiable than telegram
  4760. 07.06.2018 23:57:52, jem [@jemxpat]: 👍
  4761. 07.06.2018 23:58:01, Kyunghwan Kim - EOSeoul.io [@resvera]: +1
  4762. 07.06.2018 23:58:09, Craig Murray - EOS BlockSmith [@craigmurray100]: that would take a lot of time to onboard all those people, especially asian groups
  4763. 07.06.2018 23:58:24, Igor Lins e Silva - EOS Rio [@igorls]: most of the bps already have keybase setup
  4764. .....07.06.2018 23:58:31, Dafeng Guo - EOS Asia [@dftle]: >>invited Edward Lew - EOS Land [@ecslew]<<
  4765. 07.06.2018 23:58:34, Craig Murray - EOS BlockSmith [@craigmurray100]: "most"? based on what metric?
  4766. .....07.06.2018 23:58:44, Dafeng Guo - EOS Asia [@dftle]: >>invited Goh MEET.ONE<<
  4767. 07.06.2018 23:59:00, Ricardo Marlière - EOS Brazil [@rbmarliere]: keybase +1
  4768. 07.06.2018 23:59:13, Igor Lins e Silva - EOS Rio [@igorls]: based on 207 members we validated in the ghostbusters team
  4769. 07.06.2018 23:59:52, Igor Lins e Silva - EOS Rio [@igorls]: we can select one vote per BP official website with dns proof on keybase
  4770. 08.06.2018 00:00:17, Craig Murray - EOS BlockSmith [@craigmurray100]: if that's what everyone wants and you can get consensus
  4771. 08.06.2018 00:00:26, Craig Murray - EOS BlockSmith [@craigmurray100]: thomas is right now telling us how he thinks we are going to do it next meeting
  4772. 08.06.2018 00:00:36, ndoy |EOS Cafe: Calgary | [@n_doy]: yes for keybase, no need to reinvent the wheel. We have validated BPs there, just to make sure no duplicate e.g. between me and Syed
  4773. 08.06.2018 00:00:41, Igor Lins e Silva - EOS Rio [@igorls]: it was just a suggestion ;)
  4774. 08.06.2018 00:00:51, Craig Murray - EOS BlockSmith [@craigmurray100]: 👍
  4775. 08.06.2018 00:01:09, Douglas Horn | EOSAmericas [@DAPPerD]: Keybase is a good suggestion.
  4776. 08.06.2018 00:01:58, [email protected] [@crazybits]: [[Webpage]]https://eos.live/detail/2500 looks like this is EOS crypto-kitties called Pandafun 😁
  4777. 08.06.2018 00:02:02, Igor Lins e Silva - EOS Rio [@igorls]: and is super easy for people to cast the vote on their public folders
  4778. 08.06.2018 00:02:15, ndoy |EOS Cafe: Calgary | [@n_doy]: David says we'll use zoom poll
  4779. 08.06.2018 00:02:39, Igor Lins e Silva - EOS Rio [@igorls]: but can that prevent multiple votes per bp?
  4780. 08.06.2018 00:03:01, ndoy |EOS Cafe: Calgary | [@n_doy]: I never use zoom poll, so I'm not sure how it gets counted
  4781. 08.06.2018 00:03:21, ndoy |EOS Cafe: Calgary | [@n_doy]: unless with invite meeting maybe, using our email
  4782. 08.06.2018 00:03:50, Thomas "Disclaimer" Cox (all opinions mine) [@thomasbcox]: I want to see only one person attending PER BP
  4783. 08.06.2018 00:03:51, Douglas Horn | EOSAmericas [@DAPPerD]: Short of any unknown issue, EOSAmericas will be changing our vote to “Go” in the next vote. We will examine issue #3918 in the interim.
  4784. .....08.06.2018 00:04:52, Sherman EOSREAL [@ShermanXie]: >>invited Felicia EOSREAL<<
  4785. 08.06.2018 00:05:43, Domi - EOS Rio [@domiscd]: @thomasbcox we can use keybase, just a suggestion :)
  4786. 08.06.2018 00:06:20, ndoy |EOS Cafe: Calgary | [@n_doy]: lots of people in the zoom chat I never talk to them in any testnets channel. I'm not saying that they are not BP candidates but we do need to verify who casts vote
  4787. 08.06.2018 00:08:12, Ben Sigman [@Bensig]: [[Webpage]]https://status.producer.vote/
  4788. 08.06.2018 00:09:20, Marek EOSEmerge.io - Poland [@mbaclawski]: Then keybase is a good option
  4789. 08.06.2018 00:10:15, Denis | EOS Nation [@DenisCarriere]: If "print" is decided, we still have "no go" votes for that reason (we need to include arguments for "no" votes to filter out some votes)
  4790. 08.06.2018 00:10:47, Edward Lew - EOS Land [@ecslew]: Awesome! Thanks all of your hard working
  4791. 08.06.2018 00:11:36, James Sutherland - Cypherglass.com [@JamesSutherland]: @thomasbcox @marcantoineross @sharifbouktila — Please can I add to the agenda for the next meeting; Permission to stream these meetings publicly.
  4792. 08.06.2018 00:13:07, Nathan Rempel | GenerEOS Sydney [@nsrempel]: lol
  4793. 08.06.2018 00:13:52, James Sutherland - Cypherglass.com [@JamesSutherland]: IMHO the best way to deal with the over crowded meeting is to stream them. HoweverI WILL NOT do so unless the meeting agree to it.
  4794. 08.06.2018 00:15:01, David P - EOS42 [@GunnisonCap]: No thank you
  4795. 08.06.2018 00:15:23, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I would ask if you are not a BP taking part in the Launch , or have multiple team members from a bp in this channel please leave to make our job a little cleaner.
  4796. 08.06.2018 00:16:37, Rick Schlesinger - EOS New York [@unlockrs]: +1
  4797. 08.06.2018 00:16:39, James Sutherland - Cypherglass.com [@JamesSutherland]: Yeah, perhaps I am in the minority. But I feel like I owe it to the comunity to bring it up. Go read the Core and BIOS Boot channels. People are quite upset about the percieved lack of communication.
  4798. .....08.06.2018 00:19:34, zhangzc | Onechain [@zhangzc]: >>invited shiqi @eosstore [@shiqizhang]<<
  4799. 08.06.2018 00:20:09, Douglas Horn | EOSAmericas [@DAPPerD]: If you think people are upset about not getting much information, think how upset they would be if they saw this whole Zoom chat.
  4800. 08.06.2018 00:20:14, Lucas @EOS Beijing [@LucasEosBeijing]: welcome @shiqizhang
  4801. 08.06.2018 00:20:56, David P - EOS42 [@GunnisonCap]: People will be just fine in 24hrs when we announce a launch. Everybody just needs to relax and keep perspective here.
  4802. .....08.06.2018 00:22:16, zhangzc | Onechain [@zhangzc]: >>invited ligh-eoshcc<<
  4803. 08.06.2018 00:22:49, David Moss [@DavidMoss]: Well said
  4804. 08.06.2018 00:23:15, David Moss [@DavidMoss]: I’ve been working on this project for almost a year. It can wait another day.
  4805. 08.06.2018 00:23:35, Craig Murray - EOS BlockSmith [@craigmurray100]: Having multiple members of the same team is a problem? If we only vote once per BP group it should not matter?
  4806. 08.06.2018 00:24:10, Sam - EOS Dublin [@samnoble]: I’ll leave you to it from here on out!
  4807. 08.06.2018 00:24:12, Ren Kaidi - EOSWTZ [@FoxMr]: really sorry about that, it's my misatke 😭
  4808. 08.06.2018 00:24:32, Craig Murray - EOS BlockSmith [@craigmurray100]: for example do we kick our Marc or Alex? Both Canada, both very important, both should be here. But Canada has one vote
  4809. 08.06.2018 00:24:36, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Only one per vote obv. I don't mind if established teams want to have more than on in here until then.
  4810. 08.06.2018 00:24:50, Craig Murray - EOS BlockSmith [@craigmurray100]: ok cool
  4811. 08.06.2018 00:24:53, Craig Murray - EOS BlockSmith [@craigmurray100]: thank you
  4812. 08.06.2018 00:24:55, Nathan Rempel | GenerEOS Sydney [@nsrempel]: clarity: established hah
  4813. 08.06.2018 00:24:57, Sam - EOS Dublin [@samnoble]: Ok, then I’ll stay :)
  4814. 08.06.2018 00:25:03, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I need your Real Name and BP team on your Profile
  4815. 08.06.2018 00:25:26, Ren Kaidi - EOSWTZ [@FoxMr]: ok , i will rename it
  4816. 08.06.2018 00:25:39, Nicholas Mullesch EOS.Fish [@BitcoinRootUser]: I'll add mine as well
  4817. 08.06.2018 00:26:58, Sharif Bouktila - EOS Dublin [@sharifbouktila]: I'm not accepting direct requests from people I don't know.
  4818.  
  4819. This is the process I am following
  4820.  
  4821. If you are not in the Validation Channel and Think you need to be
  4822.  
  4823. Join this Channel https://t.me/joinchat/HbgyfBIDVpsD-2J0g9FGvQ and have someone who either @marcantoineross @xebb82 or I know and get them to recommend you in that channel for inclusion.
  4824.  
  4825. We will come up with a way to distribute the invite to trusted BPs tomorrow. It is late here.
  4826. .....08.06.2018 00:26:58, zhangzc | Onechain [@zhangzc]: >>invited ben [@cw_ben]<<
  4827. 08.06.2018 00:28:30, Emily Bush - shEOS [@emmybush]: Thanks for you work!
  4828. 08.06.2018 00:29:44, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: I'm part of a BP team, and we would like to stay. The main reason, is because we have shifts to be 24/7 to have all the information so we don't miss anything. We do understand only one of the team members is allowed to vote.
  4829. 08.06.2018 00:30:26, Craig Murray - EOS BlockSmith [@craigmurray100]: because your team can only run 1 producer node... therefore you get 1 vote in this
  4830. .....08.06.2018 00:30:51, Lucas @EOS Beijing [@LucasEosBeijing]: >>invited Lee@EOS Beijing [@shiva0187]<<
  4831. 08.06.2018 00:31:38, Stuardo Rodríguez 🇬🇹 [@stuardo_str]: Yes, I undersand the voting, we only publish one single vote per BP, and we agree 100% with it. But please do reconsider allowing more than a single member of the BP to hear/read the discussions.
  4832. 08.06.2018 00:33:52, jem [@jemxpat]: 👍
  4833. 08.06.2018 00:35:32, Sharif Bouktila - EOS Dublin [@sharifbouktila]: Ok noted, please add your BP name to your Telegram profile. Going to get some sleep now 🙂
Add Comment
Please, Sign In to add comment
Public Pastes
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!