01:39:29 imagine having the ability to hack every important twitter account and you use it to only make 120k~ 01:43:55 white hat service funded by idiots 02:26:07 doktoro: more like ~$250K 03:22:49 doktoro, and not even do anything provocative, just derail their feed to advertise your ponzi. might as well break into someone' 03:23:07 might as well break into someone's house just to take a poo 03:36:59 you're assuming that the "double your crypto" scam was the real purpose of the hack 03:37:09 could be a diversion, or part of a wider plan 03:41:47 the best part is news outlets claiming the btc was stolen. yet they gave it away. 03:42:53 you have to question the rhetoric of a society where finite assets are "insurable" by infinite fiat, yet btc that was given away was "stolen" 03:51:06 amazing that people fall for this kind of shit. I remember back when I played runescape as a child and saw someone saying they were doubling money and I knew immediately it was a scam. 03:54:37 doktoro: i remember first seeing "double your bitcoin" tor hidden service scams in like 2011 lmao, they all had urls like 22222xxxx.onion lol 03:57:22 yes yes aha aha you see you see? 03:57:52 so, its made so that the miners can effectively mandate the emission curve in some far distant future 03:58:43 say, 40 years. So, for example, lets just say in 40 years we increase the block reward from 0.6 xmr to, i dunno, 6 xmr, for a period of one year 03:59:12 in the interum, you have people positioning themselves for this .... event. Mining infrastructure, economies.... 03:59:32 its different than an airdrop because its effectively a planned era of increased money supply 03:59:53 not necessarily to holders of the tokens or whatever 04:00:43 because it would really only benefit the miners, and those who mine 04:01:26 so obviously miners are going to vote for more mining rewards. but could they hold the line for 40 years? 04:01:32 i guess that makes sense. make them give it away -> make them buy it back 04:02:11 but why does the scam have to be run by miners and not some 15 year old? 04:02:22 if the vote mechanism is something absurd like median of the last 80 years worth of blocks 04:03:09 wat? 05:17:40 Hi all :-) Is this method still an acceptable way of spending from a cold wallet with the latest version?: https://monero.stackexchange.com/questions/2160/how-do-i-use-cold-transaction-signing/5655#5655 05:28:03 I keep getting this message: 2020-07-16 05:25:41.026 W There were 22 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack, or your computer's time is off. Or it could be just sheer bad luck. 05:45:13 but my block height matches moneroblocks.info, should I ignore the message? 05:48:29 yes you can ignore 05:48:45 I have the same and it's not unusual 05:55:21 niocbrrrrrr: thanks :-) Do you know the answer to my previous question as well? 05:55:38 no 05:56:33 niocbrrrrrr: K, thanks anyway :-) 06:21:29 tryphe: imagine i stand in front of a hotel, and you drive up in your nice car, and i pretend to be the valet, and you give me your keys 06:21:39 and i drive off in your car and you never see me again 06:21:41 did i steal your car? 06:22:44 i agree that the people who lost their BTC are incredibly stupid 06:22:47 but i still think it's theft 06:23:54 there is some kind of contract implied here: give your BTC, and get 2x back. if the person offering the contract in fact intends to just take the BTC and run (which i agree should be obvious any time someone offers you such a deal), then that is theft 06:27:34 if it sounds to good to be true....................... 06:27:47 "contract" 06:43:36 jbg: I agree 06:44:10 moneromooo: Is this method still an acceptable way of spending from a cold wallet with the latest version?: https://monero.stackexchange.com/questions/2160/how-do-i-use-cold-transaction-signing/5655#5655 08:19:47 If I choose to run a node behind a reverse proxy do I need to broadcast a different port so that other nodes can connect to mine? 08:24:49 Steven_M: reading quickly, yes. Why do you think it might not ? 09:23:28 moneromooo: sorry for my late reply. just making sure because software and best practices change over time, and articles (like the one I linked) get outdated. 10:33:33 moneromooo: Follow-up question: Once a key_images file from a cold wallet is imported into a view-only wallet, is the view-only wallet turned into a full hot wallet? 10:34:31 * Steven_M goes to bed, but leaves IRC open. 10:35:36 No. 10:37:16 moneromooo: okay thanks. :-) 10:37:36 Wait. 10:38:10 I got confused. Yes. I interpreted that as "is the view-only wallet turned into a full cold wallet", since the opposite made no sense as it already is a hot wallet. 10:39:59 moneromooo: Oh, that leads me to another question, but I'll have to ask it tomorrow. 10:40:12 But private keys capable of spending XMR can't be extracted from key image I = x*Hash(x*G) 10:40:47 right? 10:40:53 Goodnight :-) 10:40:57 I believe that's what he was asking 10:41:43 Adreik: in essence yes, I was asking that 10:41:49 Goodnight :-) 10:42:01 * Steven_M goes to bed, but leaves IRC open. 10:44:02 Well, we have no idea how to extract it in a reasonable time-frame with computers and algorithms as they exist today, anyway 10:45:59 Key images are one way. Otherwise it'd be completely broken, miners could steal your money. 10:50:49 I meant that as "In principle, given *arbitrarily powerful* computing resources, one could make a brute force attempt on the key image, or use quantum computers to solve for it". 10:51:03 But such a thing is out of scope 10:53:18 If you have arbitrarily powerful computing resources, you can determine which set of input secrets and public data yield a given key image... 10:53:29 * moneromooo not sure whether there is a point here 10:59:20 It's not that it's impossible to extract the private key from the key image for an output (as I had said earlier, stating that it *can't be* extracted from the key image), it's that doing so will take as much effort as extracting finding private keys from the address and is considered impossible for practical purposes 11:02:04 Ah, pedantry, fair enough. You're right :) 11:02:53 Well, if we're being pedantic, I shuldn't say you're right. I should say I think you're mostly right. 11:07:00 On a somewhat related note to what data is safe to hand around, I am very certain (but feel it's best to check) that tx_key for proving spending is r in R=rG, the "transaction private key", *NOT* the "one-time private key" for the transaction, x=Hash(aR)+b? i.e. if you give an auditor your private view key and address, your output export file and 11:07:01 so on, and give them get_spend_proof data they can't calculate the spendkey? 11:08:24 Ah, not get_spend_proof, I mean get_tx_key 11:09:05 It is r. 11:12:05 How come if you enter "get_tx_key [transaction id of transaction you recieved]" into a watch-only wallet it can't be generated them? 11:12:08 *then? 11:12:47 Because they are randomly generated, not determinisic. 11:15:08 Right, makes sense I misread something in the whitepaper 12:58:27 Anyone use bitrefill? Is it legit? 13:05:37 bigslim[m]: i got some steam gift cards there a few years ago, no problems 13:28:57 Wondering if anyone use them more recently. Iirc I used Paxful for some Best Buy cards last fall no issues 13:41:19 Anyone know any active IRC channels that are interesting that may attract people with an interest in Monero? Relatively new to IRC. 13:44:48 #monero-research-lab, #monero-pow 13:44:55 #monero-dev 13:45:36 FSVO active/interesting :) 13:52:28 #monero-community 13:57:36 Yeah, I'm already in most of the monero channels. Was hoping for channels that werent specifically monero related :) 14:05:30 Well, ##not-monero-pools is pretty awesome 15:15:26 oh my. do i dare go in there 19:16:52 do you guys know if I need to publish my node's port if I'm serving it behind a reverse proxy? will other nodes be able to peer without issue? 19:29:47 Does connecting to the port monerod binds on from the outside connect to monerod ? 19:35:16 no 19:35:37 https://node.suchwow.xyz:443 (traefik) -> localhost:34568 (wownerod) 19:35:55 only allowing 80 and 443 inbound 19:43:35 Then no. 19:43:45 Er. 19:43:47 Then yes. 19:44:42 yes, I will need to specify the ports which my node can be reached? 19:46:59 https://git.wownero.com/lza_menace/docker-wownero/src/branch/master/wownero/docker-compose.yaml 19:47:05 this is how I'm running it now