API tools faq
paste
Guest User

Untitled

a guest
Nov 26th, 2017
71
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 58.35 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Session Start: Fri Nov 24 08:44:11 2017
  3. Session Ident: ##myriadcoin
  4. 03[08:44] * Now talking in ##myriadcoin
  5. 03[08:44] * Topic is 'Latest Wallet: 0.14.2.3 // Website: http://myriadcoin.org // Reddit: http://reddit.com/r/myriadcoin // Github: http://github.com/myriadteam/myriadcoin // Trello: https://trello.com/b/BCamm97g'
  6. 03[08:44] * Set by roarde!~roarde@pdpc/supporter/active/roarde on Mon Nov 20 20:08:12 2017
  7. -
  8. 01[08:44] FlyTheElephant is FlyTheElep@47.187.96.93 * ...
  9. 01[08:44] FlyTheElephant on ##myriadcoin
  10. 01[08:44] FlyTheElephant using barjavel.freenode.net Paris, FR, EU
  11. 01[08:44] FlyTheElephant is connecting from *@47.187.96.93 47.187.96.93
  12. 01[08:44] FlyTheElephant has been idle 2mins 41secs, signed on Fri Nov 24 08:41:46 2017
  13. 01[08:44] FlyTheElephant End of /WHOIS list.
  14. -
  15. [08:59] <irc-discord> <Mister G> I have bougt 150.000 XMY .. small stack to begin with :)!
  16. [08:59] <irc-discord> <Mister G> I am in guys .. lets get this on the road. I dont have reddit followers, but can upvote and reply!
  17. [09:02] <irc-discord> <HACK3RMAN™> @Mister G I'd recommend going here
  18. 03[09:02] * Retrieving ##myriadcoin modes...
  19. [09:02] <irc-discord> <HACK3RMAN™> https://discord.gg/GRxmM7
  20. 01[09:04] <FlyTheElephant> Are any of the people in here developers of myriad? I have the code and a small team and we are interested in helping with forking a new algo inplace of myraid-groestl due to its supposed ASIC issue.
  21. 01[09:04] <FlyTheElephant> We are also wondering if an AMA could be scheduled to discuss the coin.
  22. [09:07] <irc-telegram> Mark was added by: Mark
  23. [09:09] <irc-slack> <wlc> Dunno, but cryptapus is often here.
  24. 03[10:43] * IHAVENONICK (~zucca@85-76-32-7-nat.elisa-mobile.fi) has joined ##myriadcoin
  25. 03[11:13] * coins123 (~coins123@c-208-25.net-185.wadsl.it) has joined ##myriadcoin
  26. 02[11:13] * coins123 (~coins123@c-208-25.net-185.wadsl.it) Quit (Changing host)
  27. 03[11:13] * coins123 (~coins123@unaffiliated/coins123) has joined ##myriadcoin
  28. 03[11:16] * roarde (~roarde@pdpc/supporter/active/roarde) has joined ##myriadcoin
  29. [11:33] <irc-telegram> <illuminatiman> hey flytheelephant im not a core dev but i made myriadchain.info .. sounds awesome you should make a redditpost so your suggestion won't get lost in the chat logs.. i think itll spark a nice discussion on which algo to replace skein/myr grs and with which one.. we don't wanna rush this too fast since we really have to find an gpu only algo
  30. 02[11:44] * coins123 (~coins123@unaffiliated/coins123) Quit
  31. [11:47] <roarde> !balance
  32. [11:47] <roarde> pfft
  33. [11:47] <roarde> right
  34. [11:49] <irc-telegram> <illuminatiman> yo roarde
  35. [11:49] <irc-telegram> <illuminatiman> have u seen this
  36. [11:50] <irc-telegram> <illuminatiman> https://bitcointalk.org/index.php?topic=2140812.0
  37. [11:50] <monerobux> [ [ANN][TZC] TrezarCoin Super-Secure-PoW/PoS ] - bitcointalk.org
  38. [11:50] <irc-telegram> <illuminatiman> its a multi algo pow/pos :O
  39. [11:50] <irc-telegram> <illuminatiman> how does that work?
  40. [11:50] <irc-telegram> <illuminatiman> does it even work? 😂
  41. [12:04] <roarde> You mean the neoscrypt/sha256d/blake2s part?
  42. [12:05] <roarde> It all looks fairly standard for a hybrid attempt. NeoScrypt wasn't a very good choice, I think.
  43. [12:08] <roarde> It's not multi-algo. PoW algo is NeoScrypt. PoS submissions are signed using sha256d and the signer's privkey. Full blocks for either are signed with Blake2s.
  44. [12:08] <roarde> Or so saith the OP.
  45. [12:09] <roarde> And guys, I just *discuss* the geek part of coins because I'm developing an interest. I know very little.
  46. [12:10] <roarde> We still need capable people to create the actual code needed for algo change. Remind whomever you know that the value of those bounties seems to be rising all the time.
  47. [12:11] <roarde> Speaking of code, does anyone know what file mentions the block reward halving interval?
  48. 03[12:12] * myriad|876 (a689085f@gateway/web/freenode/ip.166.137.8.95) has joined ##myriadcoin
  49. [12:12] <myriad|876> Hi
  50. [12:12] <roarde> Hi, myriad|876
  51. [12:12] <myriad|876> Anyone here
  52. [12:12] <roarde> Hi, myriad|876 :P
  53. [12:13] <myriad|876> Can we stake myriad?
  54. [12:13] <roarde> hi
  55. [12:13] <roarde> No, it's not PoS. I doubt it ever will be. Too centralizing.
  56. [12:14] <irc-telegram> <illuminatiman> hey roarde idk where it is in the code but block halving is every 967680
  57. [12:14] <irc-telegram> <illuminatiman> blocks
  58. 01[12:14] <FlyTheElephant> http://boards.4chan.org/biz/thread/4543058
  59. [12:14] <roarde> That'll help, illuminatiman. I can grep for that figure.
  60. [12:14] <roarde> I want to truly verify.
  61. [12:14] <myriad|876> Thx
  62. [12:15] <roarde> !tip FlyTheElephant 5
  63. 01[12:15] <FlyTheElephant> the B4x development team is already working on a forking project with an algo swap, so we will be figuring all that stuff out.
  64. [12:15] <irc-slack> <wlc> roarde: consensus.nSubsidyHalvingInterval = 80640 * 12;
  65. [12:15] <roarde> (I knew the tipbot was not here, but wanted to signal anyway)
  66. [12:15] <irc-slack> <wlc> i guess
  67. [12:15] <irc-slack> <wlc> https://github.com/myriadteam/myriadcoin/blob/master/src/chainparams.cpp
  68. [12:16] <irc-telegram> <illuminatiman> and assuming 1 min blocks thats 96 weeks.. we did have 30 sec blocks at one point long ago but too many orphans and stuff so block time got doubled
  69. [12:16] <roarde> I never woulda found that, way I was going. Thanks, wlc.
  70. [12:16] <irc-slack> <wlc> yeah, saw that you mentioned grep
  71. [12:16] <roarde> That explians the 48/96 week discrepancy, then.
  72. [12:17] <roarde> How do y'all feel about average per-algo block time of 7.5 min at next change, then consider making it longer as more options (Lightning, whatever . . .) become widely available?
  73. [12:18] <roarde> So that'd be a 1.5 minute block time.
  74. [12:18] <irc-telegram> <illuminatiman> maybe depends on what the change solves tho
  75. [12:19] <irc-telegram> <illuminatiman> less orphans? prolonged supply curve?
  76. 02[12:19] * IHAVENONICK (~zucca@85-76-32-7-nat.elisa-mobile.fi) Quit (Ping timeout: 250 seconds)
  77. 02[12:19] * myriad|876 (a689085f@gateway/web/freenode/ip.166.137.8.95) Quit (Ping timeout: 260 seconds)
  78. [12:19] <roarde> Trying to get the size of the blockchain to grow a lot slower, illuminatiman. Basic overhead.
  79. [12:20] <roarde> What to do with supply curve against that is a separate discussion.
  80. 01[12:20] <FlyTheElephant> lyra2rev2 would be a good option, vertcoin is using it successfully. and groestlcoin algo is a different implementation of groestl and it does not have asics as far as I know. lyra2rev2 can be cpu mined but it is not a goo diea.
  81. [12:20] <roarde> FlyTheElephant: We have discussed "which algo" to death. What we need are implementations.
  82. [12:21] <roarde> I don't think lyra2anything is that good an option at this point. There are better ones.
  83. [12:21] <roarde> But that's a side issue. What we need is code.
  84. 01[12:21] <FlyTheElephant> B4x team will get to it as soon as we have reliable hardforking code.
  85. 01[12:22] <FlyTheElephant> Do you guys think it would be easy to get everyone to update or will we have issues hitting consensus?
  86. [12:22] <roarde> There will be consensus issues. Baikal has landed.
  87. [12:22] <roarde> So I'm thinking "substitute" is not possible. Have to take a different approach.
  88. [12:22] <irc-telegram> <illuminatiman> i think if the change benefits decentralization and promotes a value gain then ppl will come along
  89. [12:23] <irc-telegram> <illuminatiman> true baikal has landed
  90. [12:23] <irc-telegram> <illuminatiman> but since we they are mostly mining grs i think it would be in their interest to fork skein
  91. [12:24] <roarde> Right, illuminatiman, I'm thinking that's the pitch to the Baikalers: Decentral is the "why" of Myriad. Fix that again, and the value goes up.
  92. [12:25] <roarde> I see a scenario where we're gonna need a helluva lotta GPU and top-end CPU on skein to pull the switch off.
  93. [12:25] <roarde> So it would be weird to write it out.
  94. [12:25] <roarde> But, hey -- WHERE WILL WE GET THE CODE MERGES?
  95. [12:26] <irc-telegram> <illuminatiman> thats true but if we have a threshold of 75% like last time having 4/5 algos gang up on the one thats not serving its purpose should do the trick
  96. [12:27] <roarde> I'm still thinking give sha256d, scrypt, myr-gr, and skein a higher target time than the others and leave them in for now.
  97. [12:27] <roarde> Yeah, that's what I said: Run 6 or 7 algos for a bit.
  98. [12:27] <roarde> Still keep one (or one-and-a-half) minute overall block times.
  99. [12:28] <irc-telegram> <illuminatiman> hehe taht would be pretty cool and a first too
  100. [12:28] <irc-telegram> <illuminatiman> having mining consensus to add another algo
  101. [12:29] <irc-telegram> <illuminatiman> and would be first to have more than 5 algos :d
  102. [12:29] <roarde> It would be nothing to be proud of. A complexity that wouldn't be necessary, if we had attracted the right developers earlier.
  103. [12:29] <roarde> Can be fixed peaceably in post, tho.
  104. [12:34] <irc-telegram> <illuminatiman> true that does add unnecesary complexity
  105. [12:35] <roarde> Anybody here have access to the presently-viewable version of the website on the server?
  106. [12:35] <roarde> https://www.reddit.com/r/myriadcoin/comments/7f8wwa/reward_halving_96_or_48_weeks_noticed_a/
  107. [12:35] <monerobux> [REDDIT] Reward halving 96 or 48 weeks? Noticed a discrepancy. (self.myriadcoin) | 3 points (100.0%) | 1 comments | Posted by Le_Domingo | Created at 2017-11-24 - 12:27:55EST
  108. [12:35] <irc-telegram> <illuminatiman> nah i don't atleast
  109. [12:41] <roarde> Which would be cheaper to get, old scrypt or old sha256d ASIC?
  110. [12:52] <roarde> What about dropping sha256d?
  111. [12:54] <roarde> Have scrypt, myr-gr, and skein all mergeable, and together set to create 40% of the blocks?
  112. [12:54] <roarde> Add two new algos to be named later.
  113. [12:55] <roarde> So yescrypt, new A, and new B would each get 20%, for a combined total of 60%.
  114. [13:28] <irc-telegram> <illuminatiman> naa id like to keep sha256d lots of upcoming competition coming there i think sha miners will get cheaper and better
  115. [13:29] <irc-telegram> <illuminatiman> bitmain aint gonna be the only player in the space for much longer imo
  116. [13:30] <roarde> I'm thinking scrypt will outlive sha256d.
  117. [13:30] <roarde> By a bit, at least.
  118. [13:30] <roarde> Bitcoin is waking up.
  119. [13:31] <roarde> And we don't really want to promote ASIC dev. Waste of resources. There are way more boat anchors than boats already.
  120. 01[13:32] <FlyTheElephant> So yall were saying there was a previous hardfork of algo stuff, which version was that fork?
  121. 01[13:32] <FlyTheElephant> I just got done eating.
  122. [13:32] <roarde> Don't recall the version, FlyTheElephant, but yescrypt replaced qubit using a 75% consensus hard fork.
  123. 01[13:32] <FlyTheElephant> ok ill look it up
  124. [13:34] <roarde> Was probably a lot easier to do than what we have ahead of us. I wasn't here, but I figure way more than half of qubit miners were looking forward to yescrypt.
  125. [13:35] <roarde> I doubt sha256d, scrypt, myr-gr, *or* skein miners are hoping for their algo to be replaced.
  126. [13:36] <roarde> So the only one solidly with the change if it's a straight-out swap would be yescrypt, which will top out at 24% on its very best day (as would any of our algos).
  127. 01[14:01] <FlyTheElephant> So while looking over this code, it has become clear to me that it was not a hardfork, it was a softfork, and im compiling a list of all of the relevant differences and all of the mechanisms involved in the change now.
  128. 01[14:01] <FlyTheElephant> Yall are wanting this change to be done in the same manner correct?
  129. [14:04] <roarde> I'm thinking it's gonna have to be different.
  130. 01[14:05] <FlyTheElephant> I mean the consensus code.
  131. 01[14:05] <FlyTheElephant> Should we patch to a lower consensus first? If we do that we can sneak in a lower threshhold for voting in the patch before, then update the algo later with a lower threshhold.
  132. [14:06] <roarde> No one wants to lower the consensus. I didn't understand the question until you asked that.
  133. [14:06] <roarde> And no sneaking. It will be observed and rejected.
  134. 01[14:06] <FlyTheElephant> Fine by me, I am just trying to see what pepople want exactly before I start coding it.
  135. [14:07] <roarde> Great! You would do best to ask on the reddit sub.
  136. 01[14:07] <FlyTheElephant> So as far as the method of forking, the same methodology is to be repeated? Did the fork go well once consensus was reached?
  137. [14:07] <roarde> I figure now's a good time. Let the topic warm up during the holiday weekend, and get real active next week.
  138. 01[14:08] <FlyTheElephant> People aren't expecting me to program a miner or a new algo are they? Just use an existing algo from another coin?
  139. [14:08] <roarde> I think the yescrypt fork had one tiny hitch, but in toto went rather well. Not sure, you should ask further.
  140. 01[14:08] <FlyTheElephant> I'll head that way.
  141. [14:09] <roarde> Existing is preferred, but you might do well to be somewhat prepared for one algo to be more or less new, miners and all.
  142. [14:09] <roarde> Favoritism for existing is strong, tho.
  143. [14:09] <roarde> Don't know how you'd get around consensus.
  144. 01[14:10] <FlyTheElephant> Yea, I wont be programming a new algo or a new miner. I will make all of the required changes to implement another algo in there tho. and my team can test the code on the testnet.
  145. 01[14:10] <FlyTheElephant> I'm the wrong guy to write a crypto algorithm lmao. Thats a special kind of person you would need for that.
  146. [14:14] <roarde> Keep in mind that, for the bounty, you have to do everything needed in order to get the code activated, i.e. consensus and all.
  147. [14:15] <roarde> It's more than code.
  148. [14:16] <roarde> Has anyone tried renting a Baikal yet?
  149. 01[14:20] <FlyTheElephant> https://www.reddit.com/r/myriadcoin/comments/7fa2k0/algo_swap_softfork_coding_in_planning_stage/
  150. [14:20] <monerobux> [REDDIT] Algo swap softfork coding in planning stage. (self.myriadcoin) | 1 points (100.0%) | 0 comments | Posted by FlyTheElephant | Created at 2017-11-24 - 20:20:06
  151. [14:22] <roarde> nice
  152. 03[14:54] * myriad|038 (50eabe88@gateway/web/freenode/ip.80.234.190.136) has joined ##myriadcoin
  153. [14:55] <roarde> An algo swap is a hardfork.
  154. [14:55] <roarde> Old clients cannot validate blocks from the new algo.
  155. [14:56] <roarde> And blocks from old clients/miners on the old algo will be rejected, thus there's a fork.
  156. 02[14:57] * myriad|038 (50eabe88@gateway/web/freenode/ip.80.234.190.136) Quit (Client Quit)
  157. 01[14:58] <FlyTheElephant> I guess they used a softfork to gain consensus for the hardfork.
  158. 01[14:59] <FlyTheElephant> or check rather.
  159. [14:59] <roarde> Right, the new wallet would have been a softfork in itself, with the algo change point being a hardfork.
  160. 01[14:59] <FlyTheElephant> Technically v 0.11.3.1 did not change the function of the code until consensus was reached.
  161. [14:59] <roarde> Right.
  162. [15:00] <roarde> Enabling is a softfork, activating is a hardfork.
  163. 01[15:00] <FlyTheElephant> It added new rules which is a softfork, but once the rules were active a chain split occurred, but since 75% of the hashpower agreed, it is logical that the people who did not agree no longer mattered and the old chain was no longer "real" in a financial sense.
  164. [15:01] <roarde> Erm, it also turned off qubit, which makes it a hardfork.
  165. 01[15:01] <FlyTheElephant> or the old network running the old ruleset.
  166. 01[15:01] <FlyTheElephant> Yes.
  167. 01[15:02] <FlyTheElephant> Makes sense to me now.
  168. [15:02] <roarde> I don't expect it ever to make sense to me :P
  169. [15:03] <roarde> I'm just a parrot over here. All I can do.
  170. 01[15:03] <FlyTheElephant> I now have a document listing all of the changes related to the algo swap.
  171. 01[15:03] <FlyTheElephant> (all of the rest of the changes in the files related to a change in ticker from MYR to XMY, and a change in naming conventions from bitcoin to myraid.
  172. [15:04] <roarde> Be sure to ask how that process could have been better, when people reappear next week.
  173. [15:04] <roarde> Pretty sure there was something specific mentioned.
  174. [15:05] <roarde> What are you using to scan the logs? I could use a few tools.
  175. 01[15:05] <FlyTheElephant> I used winmerge on my windows box. (I code on linux)
  176. 01[15:05] <FlyTheElephant> I find winmerge to be quite pleasant to use.
  177. [15:06] <roarde> So if there were something useful in the same way on linux, you'd be using it.
  178. [15:06] <roarde> Bummer for me.
  179. 01[15:06] <FlyTheElephant> There probably is, I just don't have it and havent used it :D
  180. 01[15:07] <FlyTheElephant> I've used winmerge before and I have been happy with it before.
  181. [15:07] <roarde> It's gonna be some scripted formulation of git and diff that "everyone" knows about but you and I.
  182. 01[15:07] <FlyTheElephant> without question.
  183. 01[15:08] <FlyTheElephant> I looked for the buttons to do that on the github site but did not see it.
  184. 01[15:08] <FlyTheElephant> And I havent used git enough from the command line to feel comfortable firing off commands.
  185. [15:46] <irc-telegram> BlockchainVenturist was added by: BlockchainVenturist
  186. 03[15:48] * myriad|410 (4409feb3@gateway/web/freenode/ip.68.9.254.179) has joined ##myriadcoin
  187. 02[15:49] * myriad|410 (4409feb3@gateway/web/freenode/ip.68.9.254.179) Quit (Client Quit)
  188. 03[15:55] * silkheat (4672ed80@gateway/web/freenode/ip.70.114.237.128) has joined ##myriadcoin
  189. 03[16:00] * silkheat2 (~silkheat3@cpe-70-114-237-128.austin.res.rr.com) has joined ##myriadcoin
  190. [16:01] <silkheat2> ?
  191. 01[16:01] <FlyTheElephant> ?
  192. 02[16:02] * silkheat (4672ed80@gateway/web/freenode/ip.70.114.237.128) Quit (Quit: Page closed)
  193. [16:02] <silkheat2> I have not quit
  194. [16:03] <roarde> never quit
  195. 01[16:03] <FlyTheElephant> I smell a quitter.
  196. [16:03] <roarde> well, don't quit this
  197. [16:04] <roarde> Your doctor told you to quit that, though and she was right.
  198. [16:04] <roarde> She was wrong about quitting this, tho. Don't.
  199. [16:04] <silkheat2> damn been forever since I used an irc chat
  200. [16:04] <roarde> It's sadly gotten less silly, current convo notwithstanding.
  201. 01[16:05] <FlyTheElephant> I are see the chats. I are confused too.
  202. [16:05] <roarde> "silkheat" got on by web gateway, then fired up local IRC client as "silkheat2".
  203. [16:06] <roarde> You can expect /nick silkheat shortly, I think.
  204. 03[16:06] * FlyTheElephant is now known as silkheat
  205. [16:06] <silkheat2> took me a second to figure out the ins and out of irc again
  206. 01[16:06] <silkheat> :D
  207. [16:06] <silkheat2> had to get out the old manuals
  208. [16:06] <silkheat2> lol
  209. 01[16:06] <silkheat> I did it.
  210. [16:06] <silkheat2> like I said
  211. [16:06] <silkheat2> been a while
  212. 01[16:07] <silkheat> silkheat2 isnt the real silkheat.
  213. [16:07] <silkheat2> hmmm
  214. [16:07] <silkheat2> what the hell
  215. 03[16:07] * silkheat is now known as FlyTheElephant
  216. 01[16:07] <FlyTheElephant> Ok just type /nick silkheat
  217. 01[16:08] <FlyTheElephant> Then u can have your name back, I am done squatting.
  218. 03[16:08] * silkheat2 is now known as silkheat
  219. 01[16:26] <FlyTheElephant> roarde I have a question about the consensus algo, does it count the last x number of blocks or does it count the last x/5 number of votes of each algo?
  220. 01[16:27] <FlyTheElephant> If its last x number of blocks, then it doesnt matter if the skein people like it or not beacuse they dont mine that many blocks.
  221. [16:31] <roarde> I'm the wrong one to ask about this, but here's my likely-flawed understanding:
  222. [16:32] <roarde> The trigger for activation is that 750 of the last 100 blocks were signed with an indication in favor of the change.
  223. [16:33] <roarde> It's possible to get consensus with one algo totally opposed, provided an extremely strong majority of others supports.
  224. [16:33] <roarde> It is impossible to get consensus with two algos strongly opposed.
  225. [16:34] <roarde> 1000 blocks is a long enough span that each algo will mine very, very approximately 250 blocks.
  226. [16:35] <roarde> As far as skein coming out and in, bear in mind that a 40,000 block lead time before even signalling begins. No way are you gonna predict the right 1000 blocks that far in advance in order to not worry about skein.
  227. [16:36] <roarde> You may want to brush up on how Aux PoW was added to sha256d and scrypt. Adding that to myr-gr and/or skein may be necessary to gain acceptance.
  228. [16:37] <roarde> Would really, really, really like to *not* go there, but personally I think we're gonna have to.
  229. [16:38] <roarde> You will get better info next week. I'm new and I bring a lot of bias with me.
  230. [16:42] <silkheat> yexmy to $1 next year!
  231. [16:43] <roarde> There's only one xmy.
  232. [16:44] <silkheat> I can see it getting to $.10 without an issue
  233. [16:44] <silkheat> 150 mill market cap
  234. [16:44] <silkheat> last time I looked it owuld take about 100 or so btc buy in
  235. [16:45] <silkheat> to get it there if everything stayed the same, which it won't
  236. [16:45] <silkheat> but get the volume up like fly did with grs
  237. [16:45] <silkheat> and it will happen
  238. [16:45] <silkheat> unless I am crazy
  239. [16:45] <silkheat> which is possible
  240. [16:46] <roarde> As far as directly affecting the market via trades, purchase, etc, we're the *opposite* of fans.
  241. [16:47] <roarde> Investment instrument is not our purpose.
  242. [16:47] <silkheat> then what is exactly?
  243. [16:48] <silkheat> you wouldn't like to see it more actively traded and used while its infrastructure and community grows?
  244. [16:49] <silkheat> https://www.tradingview.com/x/G9zIeQbP/
  245. [16:49] <silkheat> healthy growth and pullback
  246. [16:49] <silkheat> the community has grown exponentially
  247. [16:49] <silkheat> a down month because of what is going on
  248. [16:50] <silkheat> don't see the down side
  249. [16:51] <silkheat> vtc' community also broguht its value up as also the number of people using it
  250. [16:58] <roarde> vtc's value came up? What makes you say that? Its exchange price is higher, but how is it more valuable now than it was before?
  251. [16:58] <silkheat> I can tell you with grs
  252. [16:58] <silkheat> much more development
  253. [16:58] <silkheat> more people on board to help out
  254. [16:58] <roarde> Note: When we get into this part of things, I'm a true outlier by far.
  255. 01[16:58] <FlyTheElephant> When trading value rises, development speed increases massively.
  256. 01[16:59] <FlyTheElephant> More people = more shit getting done.
  257. [16:59] <roarde> So the objective (and subjective) value of grs has increased. I noticed that already.
  258. [16:59] <silkheat> more people = sometimes better product
  259. [16:59] <silkheat> efor the most part when it is young, sometimes economies of scale do happen
  260. [16:59] <silkheat> but not in early life
  261. [17:00] <roarde> You say value when you mean value, and you say value when you mean price.
  262. [17:00] <silkheat> well no
  263. [17:00] <roarde> And economy of scale is horsehockey, as a fictional military officer would have it.
  264. [17:01] <silkheat> the coin has better algos, wallets, websites, infrastructure, the ability to pay devs = better value
  265. [17:01] <roarde> (I normally won't go into this stuff, but it's a quiet day. Enjoy your scrollback, Monday folks :P)
  266. [17:01] <silkheat> price does equate into that as the product is more accessible and availible with more people paying attention to it as the price increases
  267. [17:01] <silkheat> what is it you want?
  268. [17:02] <roarde> If someone is selling an item I like, and accepts only vtc, then I trade my xmy at the best vtc price available and purchase the item.
  269. [17:03] <silkheat> yes and your xmy's price is higher it will cost you less vtc for that product
  270. [17:03] <roarde> Other than that, I'd like to see trading disappear almost entirely. A *very few* traders for trading's sake keeps things realistic. We've been so very far past that point for so very long.
  271. [17:04] <roarde> The question is, what is the correct way to affect price?
  272. [17:04] <roarde> I say accept xmy for goods and services at a ratio to them that you think best.
  273. [17:05] <silkheat> to deliver a great procut with a future roadmap, new algos, development, wallets and grow the community behind it
  274. [17:05] <silkheat> that seems to be the way about it
  275. [17:05] <silkheat> all other things tend to be p&d
  276. [17:05] <silkheat> I am invested in chainlink because I believe it will bring use in the future, thus its value will be reflected in the price
  277. [17:05] <roarde> With no one motivated, nothing happens. Motivations vary. I want none of them ruled out.
  278. [17:06] <roarde> But the circle jerk is way outta hand.
  279. [17:06] <silkheat> so I am at a loss here
  280. 01[17:06] <FlyTheElephant> But the trading circle jerk is good. People come and give you money when they circlejerk after you are in.
  281. [17:06] <silkheat> if you don't care about trading, price, community use
  282. [17:06] <silkheat> what is the point in having the coin at all?
  283. 01[17:07] <FlyTheElephant> Silk has a point here.
  284. [17:07] <silkheat> if no one uses it where is its value?
  285. [17:07] <roarde> Coulda sworn I mentioned accepting it as a token of previous value in trade for goods or services.
  286. [17:07] <roarde> Though with fewer words, before.
  287. [17:07] <silkheat> there is something to be said about being altruistic, but one must be pragmatic as well
  288. [17:08] <silkheat> yes you did mention it, but if the coin has no trading price it can't be traded
  289. [17:08] <roarde> Most of me is the opposite of an altruist. Even the altruistic part wants what it wants, and often needs funds.
  290. [17:08] <silkheat> as you mentioned in vtc
  291. [17:08] <silkheat> trades
  292. [17:10] <roarde> Trading xmy for vtc, good. Trading vtc for xmy, good. Trading the proceeds for any other currency whatsoever is insane. It's time to actually *use* the token in *real* trade.
  293. [17:11] <silkheat> every coin's value is tied to the dollar though so inevitably they are all traded at their fractional rate
  294. 01[17:11] <FlyTheElephant> I am also a big fan of atomic swaps.
  295. [17:11] <roarde> You are correct, and that is bad. Doubt anyone disagrees on that.
  296. 01[17:11] <FlyTheElephant> I would prefer to avoid bitcoin and its bitmain bullshit.
  297. [17:12] <roarde> Bitcoin may mine however they land. It's their transfer fees that keeps me away from it.
  298. [17:22] <irc-discord> <Bitmintor> Any idea about segwit
  299. 01[17:24] <FlyTheElephant> roarde, I have an idea for getting the vote passed. We could offer the algo that is being removed 1000 blocks in a row with decreased difficulty so that they will want the quick blocks before we turn the lights out on them.
  300. 01[17:25] <FlyTheElephant> I think the ASIC folk dont really care that much about a coin that they only mine occasionally. If they were offered increased profits they would probably take it.
  301. [17:25] <roarde> Legbit is sometimes considered a leading indicator of whether segwit will activate, Bitmintor. It shouldn't be looked at that way, but legbit is going well enough so far, fwiw.
  302. [17:26] <roarde> Our legbit- and segwit-enabled core hasn't been released long enough to predict fully what the result will be.
  303. [17:27] <roarde> I'm gonna drop back a bit from the algo discussion for a bit, FlyTheElephant. I've had too much to say there this early on.
  304. 01[17:28] <FlyTheElephant> It looks like we have a 25% vote on skein for legbit, a 80% vote from yescrypt, 90% from myr-greostl and 0ish % from scrypt and sha256d
  305. [17:28] <roarde> Unlike earlier bitcoin, I think our community has a very strong majority in favor of SegWit. People and pools just haven't had a chance to upgrade their core daemons yet, is all.
  306. 01[17:28] <FlyTheElephant> That explains it.
  307. [17:30] <roarde> The early myr-groestl legbit support wasn't expected. But now that it's seen, it makes sense: New Baikals mining into their own wallet, which they grabbed the latest release for.
  308. 01[17:31] <FlyTheElephant> yep it ramped up fast around 2247000-2249000
  309. [17:32] <roarde> I still think skein is GPU-mineable for Myriad most of the time. ASICs are busy with coins where skein is more immediately lucrative.
  310. [17:32] <roarde> Problem is finding a skein pool running 0.14.
  311. [17:33] <roarde> If someone put one up, made real sure it was signalling legbit, and announced it, people would probably be willing to pay premium fees.
  312. [17:33] <roarde> Then you may as well shut it down when mph and zpool switch over, of course :P
  313. [17:35] <roarde> No way is skein mineable by GPU on a switching pool now. People note that and get confused.
  314. [17:36] <roarde> No reason Myriad can't be mined on skein by GPU at present. If it were done just a little bit heavily, the ASICs probably wouldn't switch to it at all.
  315. 02[17:41] * silkheat (~silkheat3@cpe-70-114-237-128.austin.res.rr.com) Quit (Quit: Leaving)
  316. [17:58] <irc-slack> <santosgpz> Hey Roarde, maybe we can get MPH to update to 0.14 again
  317. [17:59] <roarde> Actually, zpool switching their Myriad skein wallet to 0.14 wouldn't make that much difference. They're usually on DGB or whatever.
  318. [17:59] <roarde> I don't think mph did 0.14 before, did they?
  319. [17:59] <irc-slack> <santosgpz> They did, I contacted them. But then the split happened. I can reach out again.
  320. [17:59] <roarde> Thought it was just zpool, miners pool, and maybe scattered others.
  321. [18:00] <roarde> I'd wait for word from someone else for that.
  322. [18:00] <roarde> Then again, cryptapus did make 0.14 a full release.
  323. [18:01] <roarde> What I think would be super-helpful is to get an sha256d pool using 0.14 up and have it hit a few blocks.
  324. [18:02] <irc-slack> <santosgpz> Do you think its safe to push 0.14 out at this point? Considering a chain split hasn't happened that is.@
  325. [18:03] <roarde> If that didn't cause orphans, there aren't even the tiniest questions left about 0.14. It could be run safely anywhere, though exchanges will and should wait for word from the "right people". Pools could switch, no problem.
  326. [18:03] <irc-slack> <santosgpz> Ok
  327. [18:04] <roarde> I'm alone in having a concern. My concern would be baseless if an sha256d pool hit a block or two, and went along with all the other blocks in the meantime.
  328. [18:04] <roarde> a 0.14 sha256d pool, that is
  329. [18:05] <roarde> anyone got ASICs either idle or willing to switch to Myriad for a while?
  330. [18:07] <roarde> I'd go back to perusing the code, but I'm pooped out from ogling cryptonight-lite specs and code (with no good result).
  331. 03[18:10] * keepmyshirt (~myriadcoi@209.58.144.169) has joined ##myriadcoin
  332. 02[18:10] * keepmyshirt (~myriadcoi@209.58.144.169) Quit (Changing host)
  333. 03[18:10] * keepmyshirt (~myriadcoi@unaffiliated/keepmyshirt) has joined ##myriadcoin
  334. 03[19:29] * silkheat (~silkheat3@cpe-70-114-237-128.austin.res.rr.com) has joined ##myriadcoin
  335. 02[19:30] * silkheat (~silkheat3@cpe-70-114-237-128.austin.res.rr.com) Quit (Client Quit)
  336. [20:02] <irc-telegram> <EdLeed> Anyone who wants to help with a power point presentation?
  337. [20:40] <irc-slack> <santosgpz> Food for thought: https://support.bittrex.com/hc/en-us/articles/115003004171
  338. [20:48] <roarde> So, to trade at the minimum on Bittrex is to risk everything I own.
  339. [20:48] <roarde> Got it.
  340. [20:49] <roarde> (well, computers aside)
  341. [20:54] <irc-slack> <santosgpz> Looks like it. Bitnance listing anyone?
  342. [21:17] <roarde> I do see their point about ticks. Haven't examined whether their tick size is reasonable.
  343. [21:18] <roarde> santosgpz: Binance?
  344. [21:25] <irc-slack> <santosgpz> Another exchange we can try to get myriad on
  345. [21:27] <roarde> right. Binance and not Bitnance, correct?
  346. [21:28] <irc-slack> <santosgpz> Binance
  347. [21:29] <roarde> I still don't believe in spell correction in IRC, whether linked or not. Just didn't want to miss out if there was an exchange or such named "Bitnance" (empty domain, btw)
  348. [21:33] <roarde> That stuff from the Bittrex posting about "report" to the "authorities" pisses me off.
  349. [21:34] <roarde> To me that means they're gonna tell Mom or myrbot. I forget which.
  350. [21:35] <roarde> Trustless means don't recognize an "authority", rather choose for yourself or have your bots or computers figure it out.
  351. [21:35] <roarde> afaic, Bill is the only proper authority at Bittrex. If he's passing on info, he's sold out.
  352. [21:36] <roarde> I don't like pumps and such -- y'all know that. But what business is that of lawsters?
  353. 03[22:04] * myriad|636 (43b414e7@gateway/web/freenode/ip.67.180.20.231) has joined ##myriadcoin
  354. 02[22:07] * myriad|636 (43b414e7@gateway/web/freenode/ip.67.180.20.231) Quit (Client Quit)
  355. 03[23:18] * VashTheStampede (~VashTheSt@unaffiliated/vashthestampede) has joined ##myriadcoin
  356. 03[23:45] * roarde is now known as sixforty
  357. 02[23:48] * keepmyshirt (~myriadcoi@unaffiliated/keepmyshirt) Quit (Ping timeout: 240 seconds)
  358. Session Time: Sat Nov 25 00:00:00 2017
  359. [00:01] <sixforty> Please help a twit . . .
  360. [00:01] <sixforty> So I see a webpage I want to share and click "Tweet"
  361. [00:02] <sixforty> "Share a link with your followers", the url in a text box.
  362. [00:02] <sixforty> I screwed this up last time.
  363. [00:02] <sixforty> I want to make a one-line comment and have an image of the page be the rest of what's in the feed.
  364. [00:02] <sixforty> I'm clueless.
  365. 03[00:28] * sixforty is now known as Belfry
  366. 03[01:15] * Belfry is now known as wuzzabrick
  367. [01:27] <irc-telegram> <EdLeed> @sixforty, Copy the link of the page you want to share on your twitter, an image should appear below your comment box.
  368. [01:29] <wuzzabrick> It's actually the comment box part I'm confused about.
  369. [01:30] <wuzzabrick> I tried
  370. [01:30] <wuzzabrick> (comment)
  371. [01:31] <wuzzabrick> (blank line)
  372. [01:31] <wuzzabrick> (url)
  373. [01:32] <wuzzabrick> I got comment intermingled with URL text, then a graphic of the URL. Fairly messy.
  374. 03[02:06] * wuzzabrick is now known as roarde
  375. 03[02:31] * coins123 (~coins123@37.177.12.65) has joined ##myriadcoin
  376. 02[02:31] * coins123 (~coins123@37.177.12.65) Quit (Changing host)
  377. 03[02:31] * coins123 (~coins123@unaffiliated/coins123) has joined ##myriadcoin
  378. 03[02:49] * myriad|989 (88390702@gateway/web/freenode/ip.136.57.7.2) has joined ##myriadcoin
  379. 02[02:50] * myriad|989 (88390702@gateway/web/freenode/ip.136.57.7.2) Quit (Client Quit)
  380. 02[03:37] * roarde (~roarde@pdpc/supporter/active/roarde) Quit (Quit: Leaving)
  381. 02[04:15] * coins123 (~coins123@unaffiliated/coins123) Quit (Remote host closed the connection)
  382. 03[04:17] * coins123 (~coins123@unaffiliated/coins123) has joined ##myriadcoin
  383. 03[04:21] * IHAVENONICK (~zucca@85-76-32-7-nat.elisa-mobile.fi) has joined ##myriadcoin
  384. 02[05:32] * coins123 (~coins123@unaffiliated/coins123) Quit (Remote host closed the connection)
  385. 03[05:48] * myriad|074 (5f60a4f0@gateway/web/freenode/ip.95.96.164.240) has joined ##myriadcoin
  386. 02[05:48] * myriad|074 (5f60a4f0@gateway/web/freenode/ip.95.96.164.240) Quit (Client Quit)
  387. 01[08:07] <FlyTheElephant> Does anyone know what the legbit thing does?
  388. 01[08:20] <FlyTheElephant> https://www.reddit.com/r/CryptoCurrency/comments/7fffwg/myriad_has_entered_a_flat_top_triangle_usually/
  389. 01[08:20] <FlyTheElephant> https://www.reddit.com/r/CryptoMarkets/comments/7ffg0y/myriad_has_entered_a_flat_top_triangle_usually/
  390. [08:20] <monerobux> [REDDIT] Myriad has entered a flat top triangle (usually bullish) and is in the process of signaling for legbit and segwit. (https://i.redd.it/y3isvsa2r4001.png) to r/CryptoCurrency | 1 points (100.0%) | 1 comments | Posted by FlyTheElephant | Created at 2017-11-25 - 14:17:33
  391. [08:20] <monerobux> [REDDIT] Myriad has entered a flat top triangle (usually bullish) and is in the process of signaling for legbit and segwit. (https://i.redd.it/sxq7tymbr4001.png) to r/CryptoMarkets | 1 points (100.0%) | 0 comments | Posted by FlyTheElephant | Created at 2017-11-25 - 14:18:13
  392. 03[08:50] * myriad|857 (75c3f8d1@gateway/web/freenode/ip.117.195.248.209) has joined ##myriadcoin
  393. [08:52] <myriad|857> Hello fellow XMY holders. I want your opinion. At what price do you see MyriadCoin one year from now?
  394. 01[08:53] <FlyTheElephant> 200-1000 sats in my mind.
  395. [08:58] <myriad|857> And do you think it could ever reach a price of 0.0001 BTC?
  396. [09:03] <irc-telegram> <Zyzzyvas> @myriad|857, 480-500 satoshis
  397. 03[09:03] * silkheat (~silkheat3@cpe-70-114-237-128.austin.res.rr.com) has joined ##myriadcoin
  398. [09:08] <irc-telegram> <Zyzzyvas> @myriad|857, With btc at $10k, $1 myriad is possible with a lot of exposure/demand. If btc remains bullish in 2018, 0.0001 might be out of range though.
  399. [09:14] <myriad|857> Well, XMY was the first cryptocurrency I started mining so I really hope it rises to more than 1 USD (hopefully to 100 USD someday). All the best to it! Good bye.
  400. 02[09:16] * myriad|857 (75c3f8d1@gateway/web/freenode/ip.117.195.248.209) Quit (Quit: Page closed)
  401. 02[09:21] * silkheat (~silkheat3@cpe-70-114-237-128.austin.res.rr.com) Quit (Quit: Leaving)
  402. [09:22] <irc-telegram> <EdLeed> (Photo, 1185x463) http://irctelegram.myralicious.com:9090/or6XXPqA/file_155.jpg
  403. 03[11:30] * coins123 (~coins123@unaffiliated/coins123) has joined ##myriadcoin
  404. 03[11:37] * myriad|229 (6b85b8b0@gateway/web/freenode/ip.107.133.184.176) has joined ##myriadcoin
  405. 03[11:37] * roarde (~roarde@pdpc/supporter/active/roarde) has joined ##myriadcoin
  406. 02[11:39] * myriad|229 (6b85b8b0@gateway/web/freenode/ip.107.133.184.176) Quit (Client Quit)
  407. 02[11:44] * coins123 (~coins123@unaffiliated/coins123) Quit (Remote host closed the connection)
  408. 03[11:50] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) has joined ##myriadcoin
  409. 02[11:50] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) Quit (Changing host)
  410. 03[11:50] * jwinterm (~quassel@unaffiliated/jwinterm) has joined ##myriadcoin
  411. 03[11:50] * ChanServ sets mode: +o jwinterm
  412. 02[11:58] * @jwinterm (~quassel@unaffiliated/jwinterm) Quit (Remote host closed the connection)
  413. 03[11:59] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) has joined ##myriadcoin
  414. 02[11:59] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) Quit (Changing host)
  415. 03[11:59] * jwinterm (~quassel@unaffiliated/jwinterm) has joined ##myriadcoin
  416. 03[11:59] * ChanServ sets mode: +o jwinterm
  417. [12:41] <irc-slack> <mundiallover> Where is that graph from?
  418. [12:48] <roarde> !balance
  419. [12:51] <irc-telegram> <EdLeed> @irc-slack> <mundiallover, Lol i made it
  420. [12:51] <irc-telegram> <EdLeed> Coinbase
  421. [12:53] <irc-slack> <mundiallover> :+1:
  422. [12:54] <irc-slack> <mundiallover> I understand you added the Godzilla ;) but the chart looked good anyways. Often all these charts looks like crap :P
  423. 02[13:27] * roarde (~roarde@pdpc/supporter/active/roarde) Quit (Quit: Leaving)
  424. [13:33] <irc-telegram> <EdLeed> haha yeah i know. I like the one from coinbase, the only thing that bothers me is the time it takes to update. But i found a coinbase ticker for that
  425. 03[14:02] * roarde (~roarde@pdpc/supporter/active/roarde) has joined ##myriadcoin
  426. 02[14:06] * Erkan_Yilmaz (Elite18403@wikimedia/Erkan-Yilmaz) Quit (Quit: EliteBNC free bnc service - http://elitebnc.org - be a part of the Elite!)
  427. 03[14:11] * Guest25372 (Elite18403@gateway/shell/elitebnc/x-gxathyfizbtcepmm) has joined ##myriadcoin
  428. 02[14:55] * @jwinterm (~quassel@unaffiliated/jwinterm) Quit (Ping timeout: 255 seconds)
  429. 03[14:58] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) has joined ##myriadcoin
  430. 02[14:58] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) Quit (Changing host)
  431. 03[14:58] * jwinterm (~quassel@unaffiliated/jwinterm) has joined ##myriadcoin
  432. 03[14:58] * ChanServ sets mode: +o jwinterm
  433. [15:03] <@jwinterm> cryptapus: I've been having issue with v11 daemon lately where I have to kill -9 daemon sometimes
  434. [15:03] <@jwinterm> on machine running low on memory
  435. [15:03] <@jwinterm> then I can restart and it seems ok
  436. [15:03] <@jwinterm> not sure if this is to be expected if memory is low and swap is being used
  437. 03[15:42] * myrbot (~myrbot@unaffiliated/jwinterm/bot/myrbot) has joined ##myriadcoin
  438. 02[16:22] * @jwinterm (~quassel@unaffiliated/jwinterm) Quit (Ping timeout: 252 seconds)
  439. 03[17:00] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) has joined ##myriadcoin
  440. 02[17:00] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) Quit (Changing host)
  441. 03[17:00] * jwinterm (~quassel@unaffiliated/jwinterm) has joined ##myriadcoin
  442. 03[17:00] * ChanServ sets mode: +o jwinterm
  443. [17:21] <irc-slack> <eli1005> What's the best algo to mine with Nvidia
  444. [17:22] <roarde> You can try skein, eli1005, but you may end up back at yescrypt.
  445. [17:23] <roarde> We're looking at making some algo substitutions. Until then, you need ASIC to get any real return from sha256d, scrypt, or myr-gr.
  446. [17:24] <roarde> For skein, the ASICs that do that are pointed at some other coin most of the time.
  447. [17:42] <@jwinterm> !price
  448. [17:42] <myrbot> Last trade on Bittrex was at 0.00000043 BTC
  449. [17:42] <myrbot> Bittrex is -4.65% over last 24 hours on 12.190 BTC volume
  450. [17:42] <myrbot> Last trade on Cryptopia was at 0.00000045 BTC
  451. [17:42] <myrbot> Cryptopia is 7.14% over last 24 hours on 0.347 BTC volume
  452. [17:42] <roarde> Shoulda mentioned: If you do try skein, be sure you're pointed at a Myriad-only pool. If you're mining for a switcher, you'll just end up in the mix with ASIC and what-all 100% of the time.
  453. [17:45] <roarde> Looking at daemon version output, how can I tell if it's signalling legbit?
  454. [17:45] <@jwinterm> maybe getblockinfo or something
  455. [17:45] <roarde> I don't have getblockinfo. Using Insight.
  456. [17:46] <@jwinterm> oh
  457. [17:46] <roarde> Which shows algorithm and the miner's version. What part of that is legbit?
  458. [17:46] <@jwinterm> I guess it's in version bits
  459. 06[17:46] * roarde trouts jwinterm around a slap with a large bit
  460. [17:47] <@jwinterm> :P
  461. [17:47] <roarde> yeah
  462. [17:47] <roarde> *where* in the bits?
  463. [17:47] <@jwinterm> well, if it shows algo too, you can probably deduce it
  464. [17:48] <@jwinterm> since yescrypt and grs showing 80% legbit signal: https://cryptap.us/myr/myrstat/
  465. [17:48] <roarde> I think I get that.
  466. [17:50] <@jwinterm> I guess it's the 2 in the first position after 0x: http://insight-myr.cryptap.us/blocks
  467. [17:50] <@jwinterm> based on that list
  468. [17:51] <roarde> but then, where's the actual version?
  469. [17:58] <roarde> ok, fine, "2", I guess.
  470. [17:59] <roarde> The actual version I was looking for isn't software version, but *block* version, it turns out.
  471. [17:59] <roarde> I think that's one now, goes to 2 on segwit.
  472. [17:59] <roarde> Which explains why the algo digit was 1 higher than expected.
  473. [18:03] <roarde> And I still don't know of a skein pool anywhere signalling legbit.
  474. [18:04] <@jwinterm> that is block version I think
  475. [18:04] <@jwinterm> no?
  476. [18:05] <roarde> right, block version
  477. [18:05] <roarde> helluva echo
  478. [18:08] <@jwinterm> helloooo hellooo helloo hello
  479. [18:09] <@jwinterm> !balance
  480. [18:09] <myrbot> jwinterm's balance is 3,833 Myriadcoin -- see: !help
  481. [18:09] <@jwinterm> .tall
  482. [18:09] <monerobux> Bitstamp last: 8,692.00, vol: 11,634.2 | Gemini last: 8,778.61, vol: 5,088.5 | GDAX price: 8,798.99, vol: 16,451.2 | Bithumb last: 9,070.95, vol: 26,236.2 | Bitflyer last: 8,784.35, vol: 12,254.6 |
  483. [18:14] <roarde> For sha256d, what's the ratio between btc and xmy difficulties?
  484. [18:14] <roarde> ah. found a bitcoin chart
  485. [18:15] <roarde> so call btc 1,250,000,000,000
  486. [18:17] <roarde> !network
  487. [18:17] <myrbot> The current block height is: 2257519
  488. [18:17] <myrbot> The Sha256 difficulty is 62956123865.43 and the hashrate is 908873.62 Th/s
  489. [18:17] <myrbot> The Scrypt difficulty is 582931.69 and the hashrate is 8415.56 Gh/s
  490. [18:17] <myrbot> The Groestl difficulty is 7185.32 and the hashrate is 103731.71 Mh/s
  491. [18:17] <myrbot> The Skein difficulty is 7792.41 and the hashrate is 112496.01 Mh/s
  492. [18:17] <myrbot> The Yescrypt difficulty is 0.44 and the hashrate is 6.37 Mh/s
  493. [18:18] <roarde> call xmy 63,000,000,000
  494. [18:18] <roarde> !calc 63 / 1250
  495. [18:19] <roarde> .calc 63 / 1250
  496. [18:19] <monerobux> roarde: 0.0504
  497. [18:20] <roarde> .calc 1 / 0.0504
  498. [18:20] <monerobux> roarde: 19.84126984
  499. 01[18:22] <FlyTheElephant> Hey what exactly is legbit?
  500. 01[18:23] <FlyTheElephant> I have the consensus graphs, I see what is signaling what, but no amount of googling tells me exactly what legbit is.
  501. [18:24] <roarde> It will have 0.14 clients put extra info (or something) into blocks so that 0.11 clients can still sync with them, should segwit activate later.
  502. [18:24] <@jwinterm> roarde: better to make comparison between hashrate than diff
  503. 01[18:24] <FlyTheElephant> Ah, so its just a compatibility rulechange.
  504. [18:24] <roarde> Gives folks more time to switch versions if segwit activates, basically.
  505. [18:24] <@jwinterm> since block time is different
  506. [18:25] <@jwinterm> will be off by a factor of two for diff
  507. [18:25] <roarde> good point, jwinterm
  508. [18:25] <roarde> so I use 10
  509. [18:25] <@jwinterm> sha target time in myriad is 5 min
  510. [18:25] <@jwinterm> so factor of 2x
  511. [18:25] <roarde> need an ASIC that's 1/10th as good as a valid btc one
  512. [18:26] <@jwinterm> yea
  513. [18:26] <@jwinterm> we are about 10% of btc network atm
  514. [18:26] <roarde> That makes sense.
  515. [18:27] <roarde> Now how do we get them to upgrade to 0.14?
  516. [18:27] <@jwinterm> I don't know who they are, besides multipool.us
  517. [18:27] <@jwinterm> and they're not that big
  518. [18:27] <@jwinterm> afaik
  519. 01[18:27] <FlyTheElephant> Should we send some big boys with baseball bats to the pool owners house?
  520. [18:27] <@jwinterm> if you know big boys in china maybe
  521. 01[18:27] <FlyTheElephant> lol
  522. [18:28] <@jwinterm> I'm getting four new usb scrypt miners soon, so that will have literally now impact on network
  523. [18:28] <@jwinterm> :P
  524. [18:28] <roarde> How do you know what wallet version multipool.us is using?
  525. [18:28] <@jwinterm> s/now/no
  526. [18:28] <monerobux> jwinterm meant to say: I'm getting four new usb scrypt miners soon, so that will have literally no impact on network
  527. [18:30] <@jwinterm> I dunno roarde, I just thought they merge mined
  528. [18:32] <@jwinterm> the official sandwich of myriadcoin: https://i.redd.it/hzz7jr9ly4001.png
  529. 01[18:32] <FlyTheElephant> what is that thing?!
  530. [18:32] <@jwinterm> was on /r/shittyfoodporn
  531. 01[18:33] <FlyTheElephant> Is that some kinda french toast?
  532. [18:33] <@jwinterm> I think grilled cheese
  533. [18:33] <@jwinterm> plus food coloring
  534. 01[18:33] <FlyTheElephant> weird bread.
  535. [18:38] <roarde> https://www.youtube.com/watch?v=yymMEqE-Tgo
  536. [18:38] <monerobux> [ EPIC RAINBOW GRILLED CHEESE DIY! - YouTube ] - www.youtube.com
  537. 02[19:19] * @jwinterm (~quassel@unaffiliated/jwinterm) Quit (Ping timeout: 255 seconds)
  538. 03[19:26] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) has joined ##myriadcoin
  539. 02[19:26] * jwinterm (~quassel@2602:30a:c7ce:a8b0:c4b7:c401:9bcf:5cd9) Quit (Changing host)
  540. 03[19:26] * jwinterm (~quassel@unaffiliated/jwinterm) has joined ##myriadcoin
  541. 03[19:26] * ChanServ sets mode: +o jwinterm
  542. [19:39] <@cryptapus> jwinterm: I suspect your issue with 0.11 is ram limited... that sounds about like what I experienced trying to fit into a particular ram footprint... the chainindex and utxo resources of 0.11 continue to grow
  543. 03[19:44] * Guest25372 is now known as Erkan_Yilmaz
  544. 02[19:44] * Erkan_Yilmaz (Elite18403@gateway/shell/elitebnc/x-gxathyfizbtcepmm) Quit (Changing host)
  545. 03[19:44] * Erkan_Yilmaz (Elite18403@wikimedia/Erkan-Yilmaz) has joined ##myriadcoin
  546. [20:16] <roarde> If the target block time is increased, what's likely to happen with block reward?
  547. [20:16] <roarde> What happened there in going from 30 to 60 seconds; and is that pattern likely to be followed?
  548. [20:19] <@cryptapus> we didn't change block rewards. at the time, average block time was slightly higher than 60s anyways since sha and scrypt were not being mined reliably. We essentially doubled our halving time from 1 year to 2
  549. [20:20] <@cryptapus> it certainly made the code easier to maintain by just changing the block time target
  550. [20:20] <roarde> I understand that 60s was actual, but as far as target block reward halved compared to the theoretical time. Correct? (actual stayed somewhat the same)
  551. [20:21] <@cryptapus> correct
  552. [20:21] <roarde> thanks
  553. [20:22] <@cryptapus> I'm struggling with what to do about increasing the block time again once/if segwit is activated
  554. [20:22] <roarde> As long as we've gone this far . . .
  555. [20:22] <@cryptapus> just increasing the block time again is certainly the more maintainable path
  556. [20:22] <@cryptapus> extending halvings, etc
  557. [20:23] <@cryptapus> arguablly it's monkeying with emission though
  558. [20:23] <roarde> As far as wall clock/calendar time, do we want halving time to remain the same, get shorter, or get longer?
  559. [20:23] <@cryptapus> it was argued at the time that longer is more fair
  560. [20:25] <roarde> I wouldn't change block time by more than 50% until the tools to utilize the new capabilities are in everyone's hands.
  561. [20:27] <@cryptapus> I intend to offer a patch that increases block time to at least 10min :P
  562. [20:27] <roarde> I know. That's why I said something.
  563. [20:27] <roarde> Ten minutes or even more, but I think not for a good while yet.
  564. [20:28] <@cryptapus> I think perhaps the only way to make it work is complexity in the coding (sigh)
  565. [20:29] <roarde> Eventually. I'm thinking put out the fires, kick the can, make it more easily maintainable, *then* make it like it *should* be, probably departing drastically from Bitcoin.
  566. [20:29] <@cryptapus> of coarse, segwit must be activated first, enabling lightning
  567. [20:29] <@cryptapus> then a block time increase
  568. [20:30] <@cryptapus> lightning wallets should be available soon it sounds like
  569. [20:31] <@cryptapus> but I plan to move agressivly to combat chainindex bloat. To me it's more important than any algo change
  570. [20:31] <roarde> I'll buy that.
  571. [20:31] <@cryptapus> we're somewhat protected since we're over 75% mined
  572. [20:32] <roarde> Just not going out to ten minutes yet.
  573. [20:32] <@cryptapus> It could be staged... but again more complexity
  574. [20:34] <roarde> I must have something wrong: Doesn't going to ten minutes mean roughly just 12% of present income for miners?
  575. [20:34] <@cryptapus> but I want to get into a position to take advantage of chainindex optimizations coming from upstream
  576. [20:35] <@cryptapus> math could be right, essentially yes. Hence we can add complexity to increase block rewards to what they would be with 1min blocks, and adjust halvings with more complexity...
  577. [20:36] <@cryptapus> it makes things more complicated, but can be done... just don't know if it's worth the complexity
  578. [20:37] <roarde> Any valid coin with a ten-minute block time will be perceived as having a higher value than a coin with the same reward and a one-minute time. I just don't think the difference comes anywhere near 10x, as for some things the coin's way slower.
  579. [20:38] <@cryptapus> the coin's not slower with layer2 transactions though... it's actually faster.
  580. [20:39] <@cryptapus> instant (at least close to instant as advertised)
  581. [20:40] <@cryptapus> in fact confirmations would be more secure, less orphans as well
  582. [20:40] <roarde> How many different layer2's will there be?
  583. [20:40] <@cryptapus> I hear perhaps a layer3 now :)
  584. [20:40] <@cryptapus> there are currently 3 different lightning implementations that I know of
  585. [20:41] <roarde> Didn't someone mention something about complexity?
  586. [20:41] <@cryptapus> one in c, one in go, and one in java I think
  587. [20:41] <@cryptapus> complexity in the 2nd layer is acceptable IMHO
  588. [20:42] <roarde> Oh. I have no core available, and I need some blocks to hash. Checking pow's for time. What can I use for fodder?
  589. [20:42] <@cryptapus> The compelling argument I've heard is that layer1 is like TCP/IP, layer2 is like HTTP
  590. [20:43] <roarde> I don't even know how to extract blocks from a working, synced core.
  591. [20:43] <@cryptapus> well, you can run Myriad's testnet if you're looking for a short blockchain
  592. [20:43] <@cryptapus> myriad-qt -testnet
  593. [20:44] <@cryptapus> I think it's only 15k blocks
  594. [20:44] <roarde> I prefer a local file, much larger than that.
  595. [20:44] <irc-telegram> <EdLeed> @irc-slack> <santosgpz, 'member you helped me with this?
  596. [20:44] <roarde> But I'd like more of a resemblance to actual blocks.
  597. [20:44] <@cryptapus> what do you mean? something with lots of transactions?
  598. [20:45] <irc-telegram> <EdLeed> the guy said he's just doing Ethereum single mining
  599. [20:45] <roarde> Something that looks like a block with our current "normal" number of transactions. Actual blocks would be best.
  600. [20:46] <roarde> How do I extract that from a snapshot, if I can find one?
  601. [20:46] <@cryptapus> considering most of our blocks are empty, and testnet blocks are actual blocks, I would again suggest testnet
  602. [20:47] <@cryptapus> if you want a full block, fill one and mine it. it's quite possible on desktop cpu hardware
  603. 03[22:18] * silkheat (~silkheat3@cpe-70-114-237-128.austin.res.rr.com) has joined ##myriadcoin
  604. [22:32] <roarde> !network
  605. [22:32] <myrbot> The current block height is: 2257697
  606. [22:32] <myrbot> The Sha256 difficulty is 68416594847.24 and the hashrate is 987704.36 Th/s
  607. [22:32] <myrbot> The Scrypt difficulty is 499999.48 and the hashrate is 7218.30 Gh/s
  608. [22:32] <myrbot> The Groestl difficulty is 10726.07 and the hashrate is 154848.23 Mh/s
  609. [22:32] <myrbot> The Skein difficulty is 4347.74 and the hashrate is 62766.60 Mh/s
  610. [22:32] <myrbot> The Yescrypt difficulty is 0.28 and the hashrate is 4.01 Mh/s
  611. 03[22:56] * PandaNoob_ (uid54710@gateway/web/irccloud.com/x-nmjcfdcfgqmkunpd) has joined ##myriadcoin
  612. 03[23:11] * u77 (uid51820@gateway/web/irccloud.com/x-lgdqtfztjdsvwwld) has joined ##myriadcoin
  613. 02[23:36] * @jwinterm (~quassel@unaffiliated/jwinterm) Quit (Ping timeout: 255 seconds)
  614. Session Time: Sun Nov 26 00:00:00 2017
  615. 03[00:38] * myriad|546 (ad49fcb6@gateway/web/freenode/ip.173.73.252.182) has joined ##myriadcoin
  616. 02[00:38] * myriad|546 (ad49fcb6@gateway/web/freenode/ip.173.73.252.182) Quit (Client Quit)
  617. 03[00:50] * roarde_ (~roarde@pdpc/supporter/active/roarde) has joined ##myriadcoin
  618. 02[00:51] * roarde_ (~roarde@pdpc/supporter/active/roarde) Quit (Remote host closed the connection)
  619. 02[00:52] * roarde (~roarde@pdpc/supporter/active/roarde) Quit (Ping timeout: 260 seconds)
  620. 02[01:04] * PandaNoob_ (uid54710@gateway/web/irccloud.com/x-nmjcfdcfgqmkunpd) Quit (Quit: Connection closed for inactivity)
  621. [01:46] <irc-slack> <santosgpz> Skein is actually looking low lol. @edleed sorry I dont get notifications for some reason. What's up?
  622. 02[01:51] * u77 (uid51820@gateway/web/irccloud.com/x-lgdqtfztjdsvwwld) Quit (Quit: Connection closed for inactivity)
  623. 03[01:55] * coins123 (~coins123@37.177.12.65) has joined ##myriadcoin
  624. 02[01:55] * coins123 (~coins123@37.177.12.65) Quit (Changing host)
  625. 03[01:55] * coins123 (~coins123@unaffiliated/coins123) has joined ##myriadcoin
  626. [02:45] <irc-telegram> <kajafek> @roarde, lol are you kidding. the other day myriad actually had higher scrypt hash than litecoin 😂 that algo is so centralised
  627. [02:46] <irc-telegram> <kajafek> but i still say keep it because at least only 1 person in the world can 51% us using scrypt, apparently :p :p ... and they probably don't have enough sha2 ASICs, baikals, and CPUs :p
  628. 02[02:52] * coins123 (~coins123@unaffiliated/coins123) Quit (Ping timeout: 250 seconds)
  629. [05:32] <irc-telegram> Raffael was added by: Raffael
  630. 03[06:01] * jwinterm (~quassel@unaffiliated/jwinterm) has joined ##myriadcoin
  631. 03[06:01] * ChanServ sets mode: +o jwinterm
  632. 02[07:08] * @jwinterm (~quassel@unaffiliated/jwinterm) Quit (Remote host closed the connection)
  633. [08:22] <irc-discord> <Bitmintor> Can anyone shed some light on segwit and December correlation as I am new inXMY
  634. [08:23] <irc-discord> <Applet - XMY & GRS> I think it is better to ask in this discord https://discord.gg/taeAGj
  635. [08:23] <irc-discord> <Applet - XMY & GRS> I am not sure
  636. [08:24] <irc-discord> <Bitmintor> Thanks
  637. [08:24] <irc-discord> <Applet - XMY & GRS> No problem 😃
  638. [09:07] <irc-telegram> JoeyGreco was added by: JoeyGreco
  639. 03[09:33] * coins123 (~coins123@unaffiliated/coins123) has joined ##myriadcoin
  640. [10:01] <irc-telegram> <alisavtelege> (Document) http://irctelegram.myralicious.com:9090/kzjixo3v/file_157.mp4
  641. 03[10:10] * roarde (~roarde@pdpc/supporter/active/roarde) has joined ##myriadcoin
  642. [12:03] <irc-slack> Command sent from Slack by santosgpz:
  643. [12:03] <irc-slack> !network
  644. [12:03] <myrbot> The current block height is: 2258337
  645. [12:03] <myrbot> The Sha256 difficulty is 91399567874.77 and the hashrate is 1319500.80 Th/s
  646. [12:03] <myrbot> The Scrypt difficulty is 544767.16 and the hashrate is 7864.60 Gh/s
  647. [12:03] <myrbot> The Groestl difficulty is 5363.99 and the hashrate is 77437.85 Mh/s
  648. [12:03] <myrbot> The Skein difficulty is 4615.21 and the hashrate is 66628.05 Mh/s
  649. [12:03] <myrbot> The Yescrypt difficulty is 0.28 and the hashrate is 4.06 Mh/s
  650. [12:06] <roarde> Heya, santosgpz
  651. 01[12:07] <FlyTheElephant> Is there a myriad marketing imagery packet somewhere?
  652. [12:07] <roarde> there is
  653. [12:08] <roarde> forgot where
  654. [12:08] <roarde> oh. can look on trello. hang on.
  655. [12:08] <irc-slack> <santosgpz> BTC tho.
  656. [12:09] <roarde> FlyTheElephant: https://trello.com/c/YNWH35Tg/23-myriad-graphic-design-pack-vectors-and-fonts-zip-file
  657. [12:09] <roarde> @santosgpz , I talked with cryptapus a bit in the other channel about 0.14 for pools.
  658. [12:10] <roarde> Yeah, moving any possible to 0.14 is helpful.
  659. [12:10] <roarde> My opinion: Yescrypt has demonstrated it's fine. What would be nice is to have a 0.14 skein.
  660. [12:12] <roarde> Also, my own opinion: I still have unfounded reservations about recommending 0.14 wholeheartedly to pools until 0.14 sha256d hits two or three blocks and 0.14 doesn't go orphan.
  661. [12:13] <roarde> But cryptapus always > roarde; knowledge, history, reasoning, all of it.
  662. [12:13] <roarde> Does MPH have a myriad skein pool?
  663. [12:13] <roarde> Oh. And 0.14 myr-gr isn't having a problem, either.
  664. [12:14] <roarde> Any way we can get some sha256d pools on 0.14?
  665. [12:14] <irc-slack> <santosgpz> Hi roarde. Cool, yes MPH has a Skein pool. I actually threw my Vega. Up again
  666. [12:15] <irc-slack> <santosgpz> I dont think theres a single 0.14 pool up on sha256
  667. [12:15] <roarde> hitting anything, santosgpz? And is the pool you're using running 0.14?
  668. [12:15] <irc-slack> <santosgpz> *single sha-256 pool that is
  669. [12:15] <irc-slack> <santosgpz> I dont believe so
  670. [12:16] <irc-slack> <santosgpz> Let me check
  671. [12:16] <roarde> What we actually want is sha256d Aux PoW from 0.14. That's where a problem would show, should there be any remaining.
  672. 01[12:16] <FlyTheElephant> Thanks roarde, I have passed along that link and all of the sublinks to my graphics designer friend, he is gonna whip some stuff up :D
  673. [12:16] <roarde> Again, I can't show any specific reason to be concerned.
  674. [12:17] <roarde> suhweet, FlyTheElephant
  675. [12:17] <roarde> 0.14 skein shouldn't be a problem. Myr-groestl obviously isn't, after all.
  676. [12:19] <irc-slack> <santosgpz> Yeah MPH isn't mining 0.14 block. The version is still 0x005
  677. [12:19] <irc-slack> <santosgpz> I can shoot 'em another email to hopefully get them up update the pool
  678. [12:20] <roarde> If we have a few folks with bitcoin ASICs in mothballs, maybe I can get some lesser, other-coin pools to add a Myriad merge. There'd have to be traffic, tho.
  679. [12:20] <roarde> santosgpz: Obviously, yescrypt is safe. Zpool has been on it forever.
  680. [12:21] <roarde> Also, it seems most Baikal myr-gr is on 0.14, and that's working well too.
  681. [12:21] <roarde> Skein hasn't been demonstrated, but it shares more with myr-gr than with anything else.
  682. [12:22] <roarde> I'd recommend any of the above whole-heartedly. See if you can get them to try skein first, then add the other two slowly.
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!