00:13:28 Soo oguys! 00:13:31 immining eth 00:13:35 but i want monreo 00:13:51 Any pool thats converts direckly? 02:39:00 monerod[m]: You could point your gpus to moneroocean.stream. It supports mining different pow cryptonote coins and it is going to pay you with xmr. Some of them can be mined by gpu. 07:28:32 Are CN coins still profitable to mine? 07:37:04 know whether Monero will change the mining algorithm oncoming October? 07:37:05 Anybody know whether Monero will change the mining algorithm oncoming October? Anybody? 07:37:07 No 07:37:20 No? 07:37:23 No 07:37:46 No algorithm change? 07:38:11 Yes :D 07:38:24 I mean no 07:38:27 no algorithm change 07:38:27 Why? 07:38:44 Why for this time? 07:38:47 Why change? 07:39:16 The mining algorithm has always changed every 6 months. 07:39:35 Why is this time an exception? 07:39:41 No ASICs 07:39:44 No need. 07:39:57 How can i vote? 07:41:09 You can vote in November 07:41:19 But mining algorithm doesn't change anymore 07:42:36 What was the case with the hash rate rising to 2.8GH yesterday? Isn't it Asic? 07:42:40 The strategy of changing algorithm every fork is no more since RandomX was deployed 07:42:44 Canos-25, vote for what? 07:42:47 No, it's not asic 07:42:59 then what case? 07:43:39 Cloud computing hacked at large scale - 125,000 servers 07:43:56 the hacker was even kind enough to chat with us, lol 07:44:06 Wow 07:44:35 I have a very large mining farm. 07:44:48 It is now being used for Ethereum. 07:45:20 But if there are no more algorithm changes, we want to mine Monero. 07:45:33 GPU or CPU? 07:46:04 Randomx succeeded in defending the ASICs without any participation of them for a year. 07:46:04 here's the hacker's address, you can put that into supportxmr to see how much he made: 82oiMVmcV8W7yhWeK2hiDZLVNxwHcugNafCSzk9Zbs3p645n7gbHqf4TKHXrMTHXYPQffgZ9TUebKTr5ZfRN5arV4Vjtvko 07:46:17 ㅒㅏ 07:46:21 OK 07:47:46 if your mining farm is GPU you might not like monero since it's not tilted towards GPU mining 07:47:59 its just not profitable 07:50:34 GPU farms has no place in Monero mining 07:50:41 CPUs are so much more efficient 07:50:59 So from GPU farms perspective, Monero IS mined by ASICs 07:51:08 and their name is Ryzen 07:51:18 lol 07:53:06 Is using xmr-proxy heavy traffic? If 10,000 computers are connected it 07:53:33 Proxy makes just 1 connection to a pool 07:53:51 It's not heavy 07:54:04 notabotnet.jpeg 07:54:33 Aright then is the traffic between the relay server and the client heavy? 07:56:48 No, it's 1 KB/minute per connected client 08:00:12 .c 1 * 10000 * 60 * 24 / 1000 08:03:05 Is 14GB traffic consumed per day when 10,000 people connect to the xmrig proxy a day and mine? 11:00:43 tried making a transaction, but ran into “Unable to send transaction(s), no available connections”. now the tx is marked as failed in my wallet. but i can't try again as it thinks i am double spending. any ideas on how to solve? 11:04:21 Make a connection, run "relay_tx $TXID" in monerod. 11:04:37 "Failed" is odd though, I'd expect pending... 11:04:43 Is the tx in your txpool ? 11:05:43 uhhh how can i check that? 11:06:31 show_transfers does say failed 11:07:13 print_pool_sh 11:11:41 sorry, i have no idea how to send commands to monerod 11:13:30 also the tx is now old, it'll be obvious to anyone that if i resend it, it's mine 11:13:58 i'd rather make it forget about it and make a new one, if at all possible 11:16:04 Then rescan_spent and try again. I think these are unrelated issues though. 11:57:02 thanks. that doesn't work unfortunately, monerod is rejecting the new tx b/c double spend. looks like i need to clear the stale tx from the monerod pool 12:00:52 flush_txpool $TXID, if you ever find out to run them. 12:01:20 yeah, it's easy, i just need to run monerod in the foreground without --detach :-) 12:01:27 thanks for the help, friend 12:05:31 you can still issue commands when it's detached 12:07:33 as an aside, maybe soft-locking in such a way isn't very user-friendly. maybe re-send the tx when we have connections, or drop the failed tx from the pool after some time? 12:14:28 It does both. 12:14:41 not for me it didn't :'( 12:15:13 Did you wait 4 hours for the resend, or a day for the timeout ? 12:15:45 i waited... hours, but not four. should have waited more :-) sorry 12:15:59 Granted, 4 hours seems like too much. 14:51:37 well 16.0.3 isn't compiling on ubuntu 14.... probably the same error ive run into before 14:51:40 with some boost or something 14:53:06 i just need to migrate from this box its all 14:53:52 oh thats ubuntu 16 14:53:52 grm 14:53:54 hrm 14:54:37 gingeropolous: yes, there is a fix for it but only in master 14:54:57 yay 14:55:06 you can merge it yourself 14:55:09 of use newer boost 14:55:18 or use prebuilt bins 14:55:21 or upgrade os :D 14:56:13 well, i think model name : AMD Opteron(tm) Processor 6172 14:56:13 has had its run 14:56:42 thats gonna be a fun migration 15:08:44 lots of stuff on it? 15:09:12 docker ftw \o/ 15:48:34 Lets say that I have 2 QR code addresses (XMR; AEON). What happens if by mistake I try to transfer from a xmr wallet to another xmr wallet but by mistake scan the AEON wallet address instead of the XMR one. what will happen? 15:49:30 It should error out, as the QR codes monero outputs contain a "monero:" prefix. 15:49:59 If those come from third party software though, or are scanned by third party software, who knows. 15:50:59 If it somwhow does through, you should still be OK if it's a standard address since those two use the same curve etc, so you have the same secret keys underneath. 15:51:34 If it's a subaddress, I'm not sure aeon has those, but in theory you should still be able to get the coins back by patching the source. 15:51:44 Gonna be a pain though. 15:57:26 ok, got it. aeon has subaddresses. I am making wallets to be mostly offline and have subaddresses of all wallets with qrcodes printed so I can put money in there. I was wondering if I had the qr-codes nearby and scan sdt address by mistake of a different crypto... 15:57:51 sdt - dst 15:58:04 thanks 16:02:28 You can try it, with "set always-confirm-transfers 1" 16:02:36 (and cancel) 16:02:50 It should not get to the cancel part if the "monero:" prefix is in. 16:51:29 Belarus is yet another example of why citizens mesh networks will be important in the future 16:51:49 :100: 17:21:33 Inge-: what happened in Belarus? 17:22:04 fluffypony elections today 17:22:08 ah ok 17:22:14 government cut internet 17:22:56 and even cellular 17:23:11 things are about to get hot there 17:24:24 what are the radio coms that you cant pinpoint the origin of? 17:25:48 Stuff that bounces off the ionosphere is hard to trace. 17:26:06 Number stations use that. Good search term. 17:27:51 time to invest in an Iridium Go on a basic annual prepaid plan 17:28:34 it takes a bit of fiddling to get stuff setup, but you can get some basic messaging and email working pretty easily 17:36:51 why would they do that? 17:37:26 not uncommon in some countries fearing riots/disturbances 17:38:20 This one time Syria disconnected itself from the internet and everyone blamed the gov 17:38:51 years later it turned out the NSA made a mistake trying to exploit some core router, bricking it in the processs 17:39:24 So... it was the gov ^_^ 17:39:32 Heh' 17:39:33 this isn't helping my paranoia 17:39:45 https://www.theguardian.com/world/2014/aug/13/snowden-nsa-syria-internet-outage-civil-war (for reference) 17:52:39 Iran shut down cell networks during student demonstratinos some years back 17:54:28 https://servalproject.org/ 18:51:12 that serval page seems pretty dead 18:53:09 something wrong or lacking with 802.11s or 18:54:07 i haven't used it myself but just wondering 18:54:33 Only 1 hour to go for the Locha Mesh presentation: https://www.twitch.tv/monerovillage 18:55:07 You all looking for ways to use Monero without Internet should tune in to the: Monero off-the-grid 18:55:28 That seems like a cool thing to do. 18:55:48 It starts in 1 hour! 20:44:43 https://paste.debian.net/plainh/972d39ae any idea why the node can't keep outgoing connections to i2p nodes and won't bother to try anymore after ten-ish minutes? 20:46:06 same issue here, not sure yet what the cause of this is 20:46:33 i can restart my node to send transactions through the network as a workaround, but it's not great 20:48:50 vtnerd: knows maybe ^ 20:48:59 Maybe your i2p router is not very well-integrated, so your connections are not very stable? 20:49:19 what do you mean by that? anything i can do about it? 20:49:35 endor00[m]: FWIW we all have this issue 20:49:45 i have incoming connections with livetimes in the hours 20:50:04 Ideally an i2p router should stay up 24/7, and you only really become 'trusted' by the network after 24h 20:50:06 I host my I2P monero seed 24/7 and always have 0 outgoing connections, sometimes 1 20:50:23 Hmm 20:50:30 oh. yeah i've been running i2p for a long time. it consistently uses all the bandwidth i've allocated it 20:50:43 not 24/7 though 20:54:37 Every time you stop it you 'reset' the trust by other peers, so they route less traffic through you and it's harder to reach stuff 20:56:23 Btw is there any way to add a specific peer to a running monerod? 20:56:50 All I found were commands to ban or list peers 20:56:58 endor00[m]: see --add-peer, --add-priority-peer, and --add-exclusive-peer 20:57:03 But maybe I'm just blind? 20:57:07 to a *running* node 20:57:16 oh sorry :P, read over that somehow 20:57:57 selsta: has the issue been reported? any place i can follow/contribute? 20:58:31 it is on github somewhere 20:59:59 search for i2p 21:00:02 right, found it i think, 21:00:07 #6631? 21:00:35 yep 23:44:46 <[discord] Arctic#5824>: im pretty sure its something with i2p 23:45:12 <[discord] Arctic#5824>: not only time matters but i remember when setting up i2p you can give it like 50% bandwith or 100% bandwith. it will help to let it use more internet