Guest User

Untitled

a guest
May 18th, 2020
82
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 22.70 KB | None | 0 0
  1. <jwinterm> I hope you're happy
  2. <asymptotically> THANKS A LOT gingeropolous. my botnet has been gimped and now all of my children will starve to death
  3. <asymptotically> cement doesnt buy itself
  4. <jwinterm> All pull requests will be considered safe until the US dollar valuation of 1 Wownero equals $1000. After this valuation has been reached, more research will be needed to introduce experimental cryptography and/or code into the codebase.
  5. <jwinterm> pretty sure it was gingeropolous that added that to readme
  6. <jwinterm> git blame says wowario[m] but pretty sure it was ginger
  7. <niocbrrrrrr> lucky for me imma too stewpid to blame anything on
  8. * asymptotically has quit (Quit: Leaving)
  9. * cismee (~cisme_@2600:1700:7f70:2be0:10be:650b:15b6:39f5) has joined
  10. * ChanServ gives channel operator status to cismee
  11. * cisme_ has quit (Ping timeout: 244 seconds)
  12. * cismee has quit (Ping timeout: 260 seconds)
  13. * cisme_ (~cisme_@2600:1700:7f70:2be0:10be:650b:15b6:39f5) has joined
  14. * ChanServ gives channel operator status to cisme_
  15. <gingeropolous> what did i do now?
  16. <gingeropolous> .hr
  17. <gingeropolous> .network
  18. <monerobux> The current block height is 2,101,375. Difficulty is 155,686,833,943. Hashrate is 1297.39 Mh/s.
  19. <jwinterm> I thought you added that line about all PRs get merged
  20. <gingeropolous> i said no such thing. i said they will be considered safe. also, I didn't merge it in. Someone coulda swatted it down
  21. <gingeropolous> but howsat lead to asicificiasoastn?
  22. <jwinterm> .hmm I didn't read it that way and already merged PR
  23. <monerobux> https://imgur.com/eDbK1PD.jpg
  24. <gingeropolous> which PR?
  25. <jwinterm> https://github.com/wownero/wownero/pull/256
  26. <jwinterm> it doesn't fork until next february
  27. <gingeropolous> ugh
  28. <gingeropolous> well dats stupid
  29. <jwinterm> so I guess someone else could submit another PR to not switch it
  30. <jwinterm> eh
  31. <jwinterm> I'm not really sure what to do
  32. <jwinterm> I kinda think I'm coming around to the merge mining is not a good idea camp
  33. <gingeropolous> oh, is that the alternative in the face of a larger network owning a certain HW class?
  34. <jwinterm> and it would be kinda cool if wownero forked to sha3 and made open source pink and orange asics
  35. <jwinterm> https://github.com/wownero/meta/issues/27
  36. <niocbrrrrrr> do slight variations in a sha3 hash that makes them different really mean that an asic for one of them cannot be used for a different one?
  37. <niocbrrrrrr> pony said the benefit of sh3 was that it was easy to asic and therefore be more like commodity hardware
  38. <jwinterm> yea, asic can't deal with slight variation
  39. <jwinterm> but first step to open source asic would be open source fpga
  40. <jwinterm> which can handle variation
  41. <niocbrrrrrr> so pony was wrong eh
  42. <gingeropolous> it would be even cooler if wownero made a randomx asic
  43. <jwinterm> well, there are proprietary sha3 implementations available for license already
  44. <jwinterm> because it is sha3 standard
  45. <gingeropolous> or wowx
  46. <gingeropolous> think of that, ironic crypto bootstraps development of new class of CPUs
  47. <cisme_> .................................................................................................................................................................................................................................................................................................................................................................
  48. <niocbrrrrrr> I thought my 3900x was an wowsic
  49. <niocbrrrrrr> you missing one .
  50. <cisme_> .
  51. <gingeropolous> i dunno. switching to sha3 doesn't seem reckless and balls to wall enough for wownero
  52. <gingeropolous> its not wow enough
  53. <jwinterm> fair
  54. <gingeropolous> a software and network with a gaping goatse as its core splash screen demands brazen paths
  55. <gingeropolous> man, that one really got me
  56. <gingeropolous> i just didn't expect that on a terminal
  57. <jwinterm> same
  58. <jwinterm> maybe cisme_ can produce pro-asic propaganda artwork and sway opinion
  59. <jwinterm> or gaping goatse artwork
  60. <cisme_> lol
  61. <cisme_> will do if needed
  62. <gingeropolous> i think the most outlandish and reckless (but still wow) thing for wownero to do would be to find a way to get rid of pools
  63. <gingeropolous> like, there are proposals that make sense... but they work too well
  64. <cisme_> were would we swim tho?
  65. <cisme_> lakes?
  66. <gingeropolous> you think this is a school for anTSSS?
  67. <cisme_> needs to be at least 3 times this big
  68. <gingeropolous> i dunno.
  69. <jwinterm> is there any reasonable way to get rid of pools?
  70. <jwinterm> that just leads to more custodial pooling I thought
  71. <gingeropolous> i thought there was some merit to the whole hashing the blockchain thing
  72. <jwinterm> oh, making it like i/o bound so you can't feed jobs to pool miners in time?
  73. <gingeropolous> yep
  74. * semeion has quit (Quit: WeeChat 2.8)
  75. <jwinterm> there was the steem thing where miners had to sign with their private key or something to hash
  76. <jwinterm> how has no one done the blockchain hashing thing if it works?
  77. <gingeropolous> i dunno. i suspect if these things work, they work too well and no one mines
  78. <gingeropolous> but its like, im not mining wownero for the blockreward
  79. <jwinterm> that seems reckless
  80. <jwinterm> for sure
  81. <gingeropolous> and in some weird way, that might be why it works
  82. <gingeropolous> for wownero
  83. <gingeropolous> smooth once postulated that it woulda been interesting if bitcoin went the route that other p2p software went
  84. <gingeropolous> you don't get rewarded for keeping torrents up
  85. <gingeropolous> u didn';t get rewarded for seeding on napster
  86. <jwinterm> I mean, you do have a ratio, right?
  87. <gingeropolous> u did it because you wanted to fucking change the world
  88. <cisme_> the reward u felt on napster and for seeding
  89. <cisme_> is superiority
  90. <gingeropolous> i mean, sure. ratio smatio
  91. <gingeropolous> but i aint trading ratios for hookers and blo
  92. <gingeropolous> or putting them in speculative markets
  93. <cisme_> wonder if a high seed ratio has ever gotten ne one laid
  94. <gingeropolous> u don't get rewarded for running an i2p node
  95. <gingeropolous> besides getting access to the network
  96. <gingeropolous> but yeah. sha3 is fine i guess, but u might as well rename it blahnero
  97. <jwinterm> permacoin apparently tried both
  98. <gingeropolous> to the googles i go
  99. <jwinterm> Permacoin is designed such that:
  100. <jwinterm> a) payment private keys are bound to puzzle solutions – outsourcing private keys is risky for miners, b) sequential and
  101. <jwinterm> random storage access is critical for the mining efficiency,
  102. <jwinterm> thus it disincentives miners from outsourcing data. I
  103. <jwinterm> https://www.usenix.org/system/files/sec19-szalachowski.pdf
  104. <jwinterm> towards the end of that paper
  105. * cismee (~cisme_@2600:1700:7f70:2be0:10be:650b:15b6:39f5) has joined
  106. * ChanServ gives channel operator status to cismee
  107. <jwinterm> cismee, why does your internet suck so bad?
  108. <gingeropolous> so they tried both. did it work?
  109. <jwinterm> have you ever heard of permacoin?
  110. <jwinterm> randomx already uses a scratchpad, right, so just need to modify scratchpad to be 1 gb of data pseudorandomly selected from wownero blockchain, right?
  111. <jwinterm> and also make miners sign blocks with their private key
  112. <gingeropolous> who's heard of wownero?
  113. <jwinterm> yea I think that will just nethash go to zero
  114. * cisme_ has quit (Ping timeout: 260 seconds)
  115. <jwinterm> https://trends.google.com/trends/explore?date=today%205-y&q=wownero,permacoin
  116. <jwinterm> wownero wins
  117. <jwinterm> barely
  118. <gingeropolous> :)
  119. <jwinterm> for some reason ukraine really likes permacoin
  120. <jwinterm> but usa and russia love the wow
  121. <gingeropolous> i gotta re-read the cons for merge mining
  122. <gingeropolous> i mean, at the worst, it kicks the can down the road in the scenario that monero might turn stupid and wownero would need to do something else
  123. <jwinterm> the consensus in the github thread seemed to be it's onerous to pool ops and if you do it without offering a unique add-on (rootstock, namecoin, tari) then it's just a zombiecoin
  124. <gingeropolous> because that seems the one con that rings
  125. <jwinterm> which would make doge a zombiecoin
  126. <gingeropolous> oh the poor pool ops
  127. <jwinterm> fuwa at bitmain hates randomx tho, merged or not
  128. <jwinterm> and he makes most cool wownero apps
  129. <gingeropolous> really?
  130. <jwinterm> fuwa at bitmain please confirm
  131. * cisme_ (~cisme_@2600:1700:7f70:2be0:10be:650b:15b6:39f5) has joined
  132. * ChanServ gives channel operator status to cisme_
  133. <jwinterm> maybe hates was too strong https://github.com/wownero/meta/issues/27#issuecomment-626128756
  134. <jwinterm> but I feel like he's swung further to sha3 darkside since making that comment
  135. <gingeropolous> u could mod randomx enough to fit on these things: https://www.upmem.com/technology/
  136. * TheoStorm has quit (Quit: Leaving)
  137. <gingeropolous> from monero-pow, <hyc> only 32bit CPUs, not great for number crunching, but will eat up data-intensive algos
  138. <gingeropolous> i dunno if randomx would work 32 bit
  139. * cismee has quit (Ping timeout: 260 seconds)
  140. <jwinterm> that BugBud guy is totally insane in that thread
  141. <jwinterm> pretty sure niocbrrrrrr is BugBud
  142. <gingeropolous> heh.
  143. <gingeropolous> heres an idea
  144. <niocbrrrrrr> I am only on irc
  145. <gingeropolous> you make wownero merge mined but all block rewards are locked up for 100 years
  146. <gingeropolous> the ones that are mergemined
  147. <niocbrrrrrr> and 2x a month on reddddittttttt if that
  148. <niocbrrrrrr> lock wow until a person is 70
  149. <niocbrrrrrr> wait dats ng
  150. <jwinterm> then only niocbrrrrrr gets coisn
  151. <niocbrrrrrr> only I can sell them :D
  152. <gingeropolous> no that would pump the price!
  153. <niocbrrrrrr> wait orange man would probably mine then
  154. <niocbrrrrrr> I hereby direct the nsa to mine wow
  155. <niocbrrrrrr> cause reasons
  156. <gingeropolous> its a pickle indeed jwinterm
  157. <jwinterm> if you make the 2 GB scratchpad in randomx data from the blockchain, does that kill remote nodes?
  158. <jwinterm> or at least make them totally dependent on trusting the remote node?
  159. <gingeropolous> i wouldn't think so?????
  160. <gingeropolous> mining generally doesn't have anything to do with transaction creation and broadcasting
  161. <jwinterm> yea I think you're correct
  162. <niocbrrrrrr> This tech is going to "hit the reset button" on all human activity...
  163. <niocbrrrrrr> ads are getting more believable lol
  164. <niocbrrrrrr> .usd
  165. <monerobux> Monero price in USD = $66.30
  166. <niocbrrrrrr> .network
  167. <monerobux> The current block height is 2,101,404. Difficulty is 155,836,514,137. Hashrate is 1298.64 Mh/s.
  168. <niocbrrrrrr> !network
  169. <wowbux> The current block height is 212,606, difficulty is 9.90e+08, and hashrate is 3,300 kh/s
  170. <niocbrrrrrr> .c 66.3/.00376
  171. <monerobux> niocbrrrrrr: 17,632.97872
  172. <jwinterm> niocbrrrrrr, it's not that much of a difference
  173. <jwinterm> because 10x more wow coins
  174. <niocbrrrrrr> .c 17633*1298
  175. <monerobux> niocbrrrrrr: 22,887,634
  176. <jwinterm> well, like 2x right at this moment, but 10x ultimately
  177. <gingeropolous> i mean, jeff could run 1 stolen computer with a blockchain and the other 19 on a LAN and still probably be fine
  178. <gingeropolous> the latency /bandwidth is low enough
  179. <jwinterm> yea, lan pool parties
  180. <niocbrrrrrr> ok so 2,888 vs monero 1298
  181. <niocbrrrrrr> who the F is mining wow?
  182. <jwinterm> I think my miner is turned on right now
  183. <gingeropolous> jeff
  184. <jwinterm> mostly profit switcher rn https://miningpoolstats.stream/wownero
  185. <gingeropolous> oh, but we must cater to the pools
  186. <gingeropolous> because they're so damn *awesome*
  187. <jwinterm> I didn't say that
  188. <niocbrrrrrr> .c 143/2.5
  189. <monerobux> niocbrrrrrr: 57.2
  190. <qvqc> BugBud is makin brusselsprouts in my kitchen
  191. <gingeropolous> i know, im just snarkily responding to stuff in that github thread, here.
  192. <gingeropolous> for some reason
  193. <gingeropolous> because I just read them
  194. <qvqc> isn't nioc afaict
  195. <niocbrrrrrr> .c 57.2/1.7
  196. <monerobux> niocbrrrrrr: 33.64705882
  197. <jwinterm> but personally do just aesthetically like the idea of proof-of-work being as close to the thermodynamic limit as possible
  198. <niocbrrrrrr> oh it a factor of 34
  199. <gingeropolous> yeah i think thats a meme
  200. <niocbrrrrrr> mine wow!!!!
  201. <gingeropolous> to post-justify asics
  202. <gingeropolous> because corn had no choice
  203. <gingeropolous> from a previous choice of keeping things backwards / forwards compatible whatever
  204. <niocbrrrrrr> .c 22,887,634/34
  205. <monerobux> ValueError: could not convert string to float: <type 'exceptions.SyntaxError'>: invalid syntax (<unknown>, line 1) (file "/usr/local/lib/python2.7/dist-packages/sopel/modules/calc.py", line 44, in c)
  206. <jwinterm> I mean, it does make sense from the proof standpoint
  207. <jwinterm> it is more provable the less complex it is
  208. <niocbrrrrrr> .c 22887634/34000
  209. <monerobux> niocbrrrrrr: 673.1657059
  210. <gingeropolous> randomx isn't complex
  211. <gingeropolous> its big boned
  212. <niocbrrrrrr> switching all my monero hr to wow
  213. <jwinterm> .rip in peace to fellow memecoin https://bitcointalk.org/index.php?topic=1636509.msg54453833#msg54453833
  214. <monerobux> (X_X) ☜ (◉▂◉ ) we hardly knew ye
  215. <monerobux> [ [ANN][NYAN] NyanCoin - ★★★V1.3 Released!★★★ ] - bitcointalk.org
  216. <gingeropolous> i mean, you could just go extreme and make yourself the only block producers, so you stamp 1 block a day
  217. <gingeropolous> seems to work for a bunch of scam coins out there. "20 block producers, totally fine"
  218. <gingeropolous> people that vote for consensus or whatever
  219. <jwinterm> that sounds like a lot of work for me tho
  220. <jwinterm> like personally
  221. <gingeropolous> well you'd get all the blockrewards
  222. <jwinterm> yea but I already have more wow than I know what to do with
  223. <gingeropolous> sorry, im being ridiculous
  224. <gingeropolous> i dunno. it doesn't seem like something that needs to be done now though. but good to have an option in the quiver
  225. <BugBud> I think it should be Jeff that runs the one node, Jeff coin, secured by Jeff, validated by Jeff, trust no one but Jeff
  226. <gingeropolous> yay BugBud !
  227. <jwinterm> can we see a photo of jeff?
  228. <BugBud> Jeff does not use Fb
  229. <BugBud> jeff does not use instagram
  230. <jwinterm> jeff asking for wownero https://twitter.com/MollieStratton/status/1262474152377593875
  231. <monerobux> [ MollieStratton on Twitter: "… " ] - twitter.com
  232. <gingeropolous> but yeah. im never gonna be pro asic, but i get the concern of an overpowering network potentially mucking things up. well, not even network, just profit crazed miners that would pummel a poor innocent network like wownero for some cryptopennies
  233. <BugBud> I think thats part of the allure
  234. <gingeropolous> there's gotta be a better solution than just hoping some centralized entity fixes everything with magic unicorn asics
  235. <jwinterm> centralized entity would be me and wowario[m] trying to get fpga and maybe later asic code open sourced
  236. <jwinterm> seems to be current strategy
  237. <gingeropolous> yeah, but whose gonna build an asic for a level 10 memecoin?
  238. <jwinterm> https://electronics.stackexchange.com/questions/7042/how-much-does-it-cost-to-have-a-custom-asic-made
  239. <jwinterm> in a year or so NRE cost for normal asic will only be like 5 monero
  240. <gingeropolous> lol
  241. <BugBud> Think of WOW as a sort of radioactive hot potato, anybody that holds it is crazy and no one is crazy enough to hold lots of it for any extended period of time. That is how we assure a fair start. The Madman theory in action, olny the craziest survive.
  242. <niocbrrrrrr> "no one is crazy enough to hold lots of it for any extended period of time" ,= u sure about that?
  243. <niocbrrrrrr> ***umption
  244. <gingeropolous> i wonder how much wownero could be tweaked to get close to being asicable
  245. <gingeropolous> but still cpu equivalent
  246. <gingeropolous> like, you could build the asic, but the asic would perform somewhat equivalent of a CPU
  247. <BugBud> Yes Genral purpose ASICS
  248. <gingeropolous> i mean, because no matter how much randomx may be able to fend off asics, ... you can still pack more of a custom chip into one thing than you can buy a bunch of CPUs etc
  249. <niocbrrrrrr> .weather nioc
  250. <monerobux> In New York, US it is 15.57 C with a low of 13.48 and high of 17.15 C, humidity is 63%, winds of 4.6 m/s at an angle of 20 deg with clear sky.
  251. <gingeropolous> i.e., you can spend $20k on n 3900x systems, or you could buy 2 randomwow asics for that price
  252. <gingeropolous> and they'd perform about the same
  253. <jwinterm> can't you just make a PCB that has like 25 3900x sockets?
  254. <gingeropolous> i dunno
  255. <gingeropolous> why do all servers max out at 4 CPUs
  256. <gingeropolous> and those are rare
  257. <gingeropolous> ud think there'd be more of them, because, yeah, scale.
  258. <niocbrrrrrr> how to schedule ram access
  259. <niocbrrrrrr> shot in the dark
  260. <gingeropolous> because i personally think that "the good guys" should design a randomx asic before the "bad guys" do, and open source it
  261. <gingeropolous> scorched earth policy
  262. <jwinterm> Motherboards are limited by the limitations of the Integrated Memory Controller found on all modern CPUs.
  263. <niocbrrrrrr> super computers are basically lots of lesser things ties together
  264. <jwinterm> Most Intel and AMD desktop CPUs (e.g. Ryzen, Core i7, i5, etc) have a limit of 2 memory channels with 2 DIMMs per channel. This means that a motherboard can only have up to 4 DIMM slots when designed for one of these CPUs.
  265. <niocbrrrrrr> ties
  266. <niocbrrrrrr> tied
  267. <BugBud> Its such a waste to produce a bunch of ASICs that are useless for anything else. Its really nice to be able to turn your machine to doing something else when you want to or if you want to resell it.
  268. <gingeropolous> so if CPUs are 100%, and the good guys can make a randomx asic thats 200%, supposedly they've maxed out the headroom for further gains
  269. <gingeropolous> so that leaves the bad guys only the last 10% of gains
  270. <gingeropolous> to 210% or whatever
  271. <gingeropolous> prolly no manufacturer is gonna invest for 10%
  272. <jwinterm> yea but randomx is so complex that will always be much more of an open question than sha3 or whatever
  273. <jwinterm> it just is
  274. <gingeropolous> well, randomwow could be modded to be less complex
  275. <gingeropolous> i mean, if asic manufacturers have a grab bag of stuff that you can clobble together, we could figure out which ones are cheapest
  276. <gingeropolous> so it ends up being a super dumb CPU. I dunno
  277. <gingeropolous> this is like getting into CPU design
  278. <jwinterm> yea, maybe randomwow tuned down to make it easier on mobile people and also change scratchpad to use blockchain so kill pools
  279. <jwinterm> for next year or three
  280. <gingeropolous> i wonder if tevador would be intrigued
  281. <jwinterm> right, well CPU design is all proprietary IP
  282. <BugBud> Not so
  283. <BugBud> Open Power
  284. <BugBud> Power 9
  285. <jwinterm> who's mining wow on risc-v?
  286. <jwinterm> or mining anything?
  287. <gingeropolous> well, an ASIC is a CPU
  288. <jwinterm> that is semantics and it's wrong
  289. <gingeropolous> no, the other way around is wrong :P
  290. <BugBud> You get great heashrate on an open power system today with Monero
  291. <niocbrrrrrr> sucks vs ryzen
  292. <niocbrrrrrr> I'll keep pulling
  293. <gingeropolous> ""Normal" ASIC: In this solution, you are designing things down to the gate level. You take your VHDL/Verilog and compile it. The design for the individual gates are taken from a library of gates & devices that has been approved by the chip manufacturer (so they know it works with their process). "
  294. <gingeropolous> i mean, if this library thing is real, it seems you could take the union of CPU stuff and ASIC library stuff and find where a modded rx might be asicable
  295. <jwinterm> yea but you don't get to see the library
  296. <BugBud> In its current state, the RandomX implementation does have support for POWER crypto acceleration, but it lacks the JIT support of x86 and arm64. The README states the JIT has at least 10x of an effect on hash rates.
  297. <jwinterm> will move conversation to github thread for posterity
  298. <BugBud> No plans to switch to SHa-3 should be laid before an open source miner is actually fully available otherwise its just a ploy by Jihan WOW to pwn the ecosystem
  299. <jwinterm> the switch is flagged for feb 2021 right now
  300. <jwinterm> I'm sure we can get open source fpga done by then
  301. <jwinterm> and if not can reflag
  302. <BugBud> That should be removed and the ASIC should be out for a while before assuming we will have one and jumping the gun
  303. <rottensox> <@jwinterm> I kinda think I'm coming around to the merge mining is not a good idea camp
  304. <rottensox> praise be!
  305. <BugBud> Also for all the reasons Monero users hate ASICs ( so much out there ) we shouldnt go down that road
  306. <jwinterm> I am a monero user that doesn't hate asics
  307. <jwinterm> fwiw
  308. <niocbrrrrrr> burn him!!
  309. <jwinterm> to me it seems like the logical conclusion of proof-of-work
  310. <jwinterm> I get wanting to keep general purpose for distro
  311. <niocbrrrrrr> going outside to check for zombies
  312. <BugBud> The point is you have seen the arguments put before the community. The choice not to go with Asics comes from a desire not to have a centralized coin with very few miners and even open source ASICs wont really change the fact that people will not want to get asics just to mine WOW. Lots of value in getting people to mine tiny amounts on CPUs so that many people can get some amount. That aspect of the
  313. <BugBud> distribution is important to the network effect.
  314. <BugBud> I can tell anyone to go mine some WOW, sure its not allot but it gets it in their hands. With time they mostly decide they want more and buy some.
  315. <jwinterm> I get it, however it is also dominated by profit switching pools and one hour block times are not uncommon because of this
  316. <BugBud> I think SHA-3 wont hold a candle to future optical proof of work implementations.
  317. <jwinterm> and it sucks to verify on mobile
  318. <BugBud> I feel like remote node is a fine solution for mobile
  319. <BugBud> Rapid growth and improvement in silicon photonics over the last two decades has led to the commercialization of silicon photonic co-processors (integrated circuits that use photons instead of electrons to perform specialized computing tasks) for low-energy deep learning. oPoW is optimized for this technology such that miners are incentivized to use specialized, energy-efficient photonics for computation.
  320. <BugBud> Beyond providing energy savings, oPoW has the potential to improve network scalability, enable decentralized mining outside of low electricity cost areas, and democratize issuance.
  321. <jwinterm> spreading the virus https://www.reddit.com/r/CryptoCurrency/comments/gmdmc4/daily_discussion_may_19_2020_gmt0/fr3bnfr?utm_source=share&utm_medium=web2x
  322. <monerobux> [REDDIT] Daily Discussion - May 19, 2020 (GMT+0) (self.CryptoCurrency) | 5 points (100.0%) | 38 comments | Posted by AutoModerator | Created at 2020-05-19 - 00:09:18
  323. <jwinterm> remote nodes kinda suck on monero
  324. <jwinterm> and is dependent on people running remote nodes for free just because
  325. <BugBud> Remote nodes work pretty well on Monero
  326. <BugBud> tend to disagree with you there
  327. <jwinterm> they're ok, they suck compared to electrum
  328. <jwinterm> because you still have to scan every block
  329. <BugBud> load up Monerujo it works fine
  330. <jwinterm> yea it just takes 10-20 min to catch up if you haven't opened it in a month or three
Add Comment
Please, Sign In to add comment