04:18:57 hey peeps, I was just looking at a thread here https://github.com/monero-project/monero/issues/6639 and it says: "An owner of this repository has limited the ability to comment to users that have contributed to this repository in the past.". Is there any way I can get permissions to comment please? 04:20:44 knaccc: pm luigi your github email 04:20:55 selsta cool, thanks 04:21:24 was there a spam attack on the repo? 04:21:34 yes 16:27:18 Word of guys running Monero community should be BELIEVED. Why would anyone that stole money and laughed at the losers that took the bait ever have a reason to lie to you? http://removeddit.com/r/Monero/comments/6d6okb/fluffypony_needs_to_give_up_his_commit_access_and/ (changed link to removeddit since /r/monero mod removed to try to cover it up - maybe fluffy himself?) 18:49:34 Is there a way to get a list of all pending Monero transactions (transactions in mem-pool) via the Daemon RPC? 18:49:56 I see "get_txpool_backlog" but I'm not sure what to make of the output. 18:50:34 If XMRChain.net can do it, there has to be a way 18:50:53 get_transaction_pool_hashes 18:51:15 Or get_transaction_pool if you want the whole data. 18:51:42 The list of RPC is in src/rpc/core_rpc_server.h 19:02:39 curl http://127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transaction_pool"}' -H 'Content-Type: application/json' leads to "message": "Method not found" 19:03:45 https://www.getmonero.org/resources/developer-guides/daemon-rpc.html#get_transactions 19:03:53 curl http://127.0.0.1:18081/get_transactions -d '{"txs_hashes":["d6e48158472848e6687173a91ae6eebfa3e1d778e65252ee99d7515d63090408"]}' -H 'Content-Type: application/json' 19:04:28 actually https://www.getmonero.org/resources/developer-guides/daemon-rpc.html#get_transaction_pool 19:04:32 see an example there 19:12:32 Ah, I see, I ran: curl http://127.0.0.1:18081/get_transaction_pool -H 'Content-Type: application/json' and I just get the following: https://pastebin.com/hUhm2szn 19:12:32 Which isn't the expected output. When you run it, do you get the expected output? 19:15:26 Yes. 19:15:39 Hmmm 19:15:41 Are you sure your txpool isn't empty ? :) 19:17:42 I reset my node and now I'm getting information. Strange! 19:18:18 I'm going to add these non-JsonRPC endpoints to my C# library. 19:20:15 My end goal is to build a Twitter bot that makes posts about "Strange" Monero Transactions. For example if I see a transaction in the memory pool with a ring size of 500, that is out of the ordinary. 19:20:28 Will spend time brainstorming what is considered "Out of the ordinary" when I get there. 19:20:40 you might be waiting a long time to see a tx with a ring size like that :D 19:22:07 I remember one time I saw some 249 ring-size transaction. Hopefully this Twitter bot can be used to keep people in-check (i.e. putting them on-blast to encourage them to create transactions that conform to the norm, so they don't stick out among the herd) 19:24:25 I think you'll find it hard to tell who made a tx ^_^ 19:25:41 I mean, if you want to prod the person who made the tx, posting it on some chat site isn't going to reach that person, is it. 19:26:15 so you're doing it for fun, not to warn the person. 19:28:59 Yeah I guess it's for fun, the person wouldn't know unless they follow the Twitter account. It will serve the purpose of making people nervous to encourage good behavior by pointing at transactions that stand out. Maybe the person who makes the non-standard ring-size transaction will start to sweat if they see their transaction on the Twitter 19:28:59 account's radar 19:33:21 Isthmus probably has a list of things to look out for. 19:56:39 Mmmmmmmmmm ring size is fixed to 11 by network consensus 19:56:58 Maybe you mean transaction with 500 inputs? 19:56:59 I remember being able to set it yourself as well via CLI. Was this changed? 19:57:08 You can't change ring size anymore 19:57:26 Okay, because it was definitely the ring-size being 500. This was over a year ago as well 19:57:30 specifically for this reason - to not make your tx stand out 19:58:51 You can still have varying ring sizes when spending unmixable pre-rct outputs. Though that won't be 500. 19:59:35 Technically ^_^ 20:00:32 Imagine identifying a transaction with an unlock time of ulong.MaxValue. That would be a funny Tweet. 20:00:39 Diamond hands... 20:17:49 Yeah Mmmmmmmmmm there are several types of fungibility defects that could make for fun alerts 20:18:00 I’m on my phone but lemme see if I can find links 20:19:04 Isthmus: perhaps I could add to https://fungibility.fail? it currently just points to seth's great fungibility graveyard 20:20:05 Isthmus Can I email you so we can have a more structured communication channel? If so, what is your email? 20:22:43 Yea for sure: Isthmus (at) getmonero.org 20:23:08 WOAH this fungibility graveyard is awesome 20:23:13 👀 20:25:17 I’ve got a running list of candidates here: 20:25:19 https://www.overleaf.com/read/bxbpmwxgskjw 21:15:37 Who was working on that new official monero gui wallet feature that would scan a qr code image? 21:15:54 And what branch is the code located on 21:26:44 anon_82641[m]: scan using camera or scan from screen? 21:26:59 Scan from screen without camera 21:27:21 it should be included in the latest release 21:27:44 Amazing great work 21:27:53 Im going to test it then 22:40:41 Always looking for new entries 😉 23:13:12 Demo found here: https://www.reddit.com/r/Monero/comments/myk0hb/monero_tv_prototype/ 23:16:18 new numbers folks: https://twitter.com/utxobr/status/1386458317405540360 23:16:43 per-country stats too - https://twitter.com/utxobr/status/1386458785363935236 https://twitter.com/utxobr/status/1386458962543923201 23:17:42 "reachable" == able to `connect()` _and_ responds to p2p handshake