00:57:36 Hello, gentlemen 01:01:24 I want to make a memecoin for laughs and giggles using Monero, basically just change the name. No fake monero bs. Something kinda like doge. I know there's things that are easier to fork, but Monero monero is using the fairest mining system, free of ASICS. If I am to make this memecoin it is very important to me to give regular people a fair chance 01:01:24 at mining it. Would doing this be very hard, or quite simple? Do any of you think you could help me out? I cannot find a single guide on how to do it. 01:01:54 Have you heard of Wownero? 01:01:58 Thats exactly what you're describing :) 01:02:50 Guest_53: search monero.stackexchange.com 01:03:01 but no, there is no tutorial on how to fork monero 01:04:23 Seth thank you for taking the time to respond. I just checked out Wownero and that's pretty much what I want but with a famous meme as a logo and name. Do you reckon I can use a file comparison program to compare differences between the two and thus be able to find where differences have to be applied? 01:05:03 Not sure honestly, but would be a good learning experience for you to work on forking things 01:05:21 As selsta said try looking around SE and other sources for more info on how to do that, but there isn't a guide per se 01:05:53 selsta thank you as well for your response, i have already searched stackexchange quite intensively and did not find what i am looking for 01:06:14 You're probably just gonna have to wing it honestly 01:06:35 devs are busy building overall, and normally dont have time to help someone fork their code, when it usually wont end up in contributions back to the forked repo 01:07:31 ill try comparing the codes of wownero and monero for now - but i have a feeling i will be here again in the future. i hope you guys dont mind what would seem to you a bunch more stupid questions in the future :( 01:07:38 fwiw this channel is about monero development, no one will explain it to you here 01:07:42 you might try in #monero 01:07:47 Yeah ^^ 01:08:05 Don't want to clutter up this channel with fork convos, but maybe people will be generous to help in #monero 01:08:28 thank you gentlemen 01:08:31 i will do that 01:08:36 group hug? 01:08:42 * dsc_ hugs 01:08:51 * sethsimmons hugs 01:08:54 *hug* 01:10:09 before i leave and bid you fine gentlemen the best of days, i will leave these kind words behind: MONERO GIRL IS BEST CRYPTO WAIFU. good day, gentleme and gospeed 04:48:05 Running get_transfers against my wallet rpc returns very few (3) sent txs, while in reality I've sent hundreds. Does the wallet prune sent txs? If so, how do I disable this? 04:50:08 I am also unable to get_transfer_by_txid for txids I know that I sent, returns error Transaction not found 11:24:00 The wallet does not prune sent txes. Check your parameters are sane. 11:48:44 hey, i wonder, without being sure of technical feasibility of this, whether the topic of incentivizing nodes that are online has been discussed previously 11:49:12 miners get all the action, but without nodes there would be no network either. makes sense in theory that nodes are rewarded too? 11:49:30 you have an incentive to run a node as it increases your privacy 11:49:38 if that's not feasible to implement, how about a small surcharge on top of the network fee to incentivize public nodes? 11:49:44 I do, personally 11:50:05 there is the pay-for-rpc system that public nodes can use 11:50:07 your average monero user doesn't (if not now, if we see much more adoption), and probably doesn't even know how 11:50:19 is that the hashes thing? 11:50:27 yes, it pays the node operator in hashes 11:50:52 i read smt about it but never really looked into it 11:51:08 will the wallet honor it automatically if it's set on the server? 11:51:20 https://www.monerooutreach.org/stories/RPC-Pay.html 11:53:55 reading 11:55:08 Once the CLI wallet is initiated, typing start_mining_for_rpc will start the RPC-Pay process 11:55:21 i skipped ahead to the example, so maybe the answer is elsewhere in the text 11:55:36 but will the server allow access even without typing this? 11:56:01 ah, is it a one-time thing and then whenever the wallet is on it's racking up credits 11:56:09 fuck, might as well just try it 11:56:10 lol 12:02:10 E Payment address may not be a subaddress: 12:02:12 lol 12:02:24 that's rather arbitrary :p 12:02:47 mining also does not allow subaddress, maybe that’s why 12:04:35 It comes only when a client provides a hash that can mine a block, while the server’s output must be continuous, matching the regular provision of hashes. 12:04:38 this I didn't understand 12:04:48 must the server be mining too? 12:06:09 Error: refresh failed: payment required.. Blocks received: 0 12:06:10 --> ok, that answers that 12:07:09 disconnecting and reconnecting after start_mining_for_rpc makes it not refresh once again. wouldn't it make more sense to remember which servers we've connected to and automatically enable it on wallet open if it's been enabled before? 12:07:40 if i've opened the wallet then i'm intending to use it, and if i've allowed it before, i'll likely want it allowed now (or it won't work, and then opening the wallet makes no sense) 12:09:54 I can’t help, I didn’t test this yet as I don’t intend to run a public rpc node. 12:09:56 so just how many such credits on average would a server need to find a block? 12:18:44 Error: Error mining to daemon: Found nonce, but daemon errored out with error -18: Stale payment, continuing 12:18:47 hm 12:20:03 seems to happen with persistent-rpc-client-id 1 12:20:59 it was unclear how to "mine on a better device to spend credits on low-end device", any idea how to try that? 12:21:18 because judging from my laptop fan right now, it would be a poor idea to connect mobile devices to this power-hungry monster 14:26:43 .merge+ 6111 6600 6607 6610 6613 6690 6731 6746 6752 6753 6757 14:27:01 .merge 6111 6600 6607 6610 6613 6690 6731 6746 6752 6753 6757 14:27:46 Anyone remembers the right syntax ? 14:27:53 how ring members are chosen in Monero? 14:28:21 Randomly according to a gamma a distribution. 14:28:30 ring member need to be unspent output? 14:28:45 or it can be even spent output? 14:28:56 It can be either. 14:29:12 .merges 14:29:12 -xmr-pr- 6111 6600 6607 6610 6613 6690 6693 6731 6746 6752 6753 6757 14:29:22 ok thanks 14:29:28 Oh, excellent, less spammy. 14:30:27 Any opinions on 6693 (boost version bump, though no particular reason apparently) 14:31:02 Also 6615/6616. This changes the db format. I coded that ages ago now. 14:52:28 db format change would imply a database conversion for 0.17 right? 14:53:03 Yes. 14:53:34 You know what, let's leave it for later. I don;t even remember the db changes. 17:43:49 moneromooo: can we add #6771 early to fix depends build system and travis? 17:43:57 thecharlatan also verified the diff from the new repo 17:58:39 .merge 6771 17:59:13 .merge+ 6771 17:59:13 Added 18:11:15 xiphon: did you see the log I dropped in yesterday? 18:11:40 has there been any progress regarding the 26 word mnemonic seed proposal? 18:12:14 charuto: no plans for 26 word seed 18:12:20 14 word seeds is considered 18:12:34 so no block height encoding? 18:12:50 with block height encoding https://github.com/tevador/monero-seed 18:13:16 interesting, thanks for the link 18:19:53 any idea how many bits of data do the current 25 word mnemonic seeds contain? 18:20:30 more than the 14 word seed, i assume 18:20:44 unless the word dictionary on the 14 word seed is gigantic 18:25:09 256 18:25:14 and the smaller seeds are 128 18:31:13 so thats more than 100 bits of data "lost", aren't we giving up keyspace like that? 18:32:06 it says "128-bit seed provides the same level of security as the elliptic curve used by Monero." 18:32:14 not that I understand it :P 18:32:47 charuto: what do you mean 100 bits of data are lost? 18:34:45 see also corresponding discussion, tevador goes into it in more detail https://github.com/monero-project/monero/issues/6639 18:36:16 the 14 word seed proposal has 154 bits of data, the current 25 word seed has 256 bits. surely you can't fit the same number of private keys on the 14 word seed 18:36:23 but maybe it's going over my head and there's a way to do it 18:37:52 in the 14 word seed* 18:44:42 these is no practical way to fit 256 bits into a 14 word seed - you'd need 18:44:50 a wordlist with 319 558 words 18:44:59 actually more, because we want a checksum 18:45:03 so it has to fit into 13 words 18:45:31 the wordlist has to be 847 180 words long 18:46:17 "the Oxford Dictionary has 273,000 headwords; 171,476 of them being in current use, 47,156 being obsolete words and around 9,500 derivative words included as subentries." 18:46:26 so well short of the 847k we'd need 18:53:11 We can use unicode code points. Lucky for us who don't speak 30 languages, unicode has addd plenty of image spam. 18:54:10 I wonder if they ever thought of adding video code points once they start to get out of stuff to add and want to keep their job going again. 18:55:05 You forget about their emoji stuff 18:55:22 What better way to encourage expression than to have a committee approve it piecemeal? 18:57:42 Wait. They have more images than just those ? 18:58:07 I don't know how Unicode emoji work. I don't ever use them 18:58:22 I enjoy using words that don't have to go through a Unicode committee 18:58:55 Well, their work on glyphs was really useful, before they had to try to keep themselves in a job. 18:59:37 The whole idea of an emoji approval process really rubbed me the wrong way 19:00:03 It felt like trying to be a gatekeeper of expression, which seems... wrong 19:00:30 Obviously supporting a broad range of character types is essential 19:00:35 But this feels very different 19:20:39 oh I mean if we're serious about this 19:20:45 then we should do the wordlist in Korean 19:20:49 1.1m words 19:21:41 And we'd have won. 19:21:42 Finnish might work, 800k words in RedFox and that doesn't include inflections 19:23:53 Iirc they have a boatload of similar looking words lol 19:23:57 Finnish that is 19:26:13 That's because they can never remember how to finish them. 19:26:20 LOL 19:26:28 Only got me two tries. 19:39:21 why are words used? because theyre easy to note down? 14 words isn't memorable, emojis aren't memorable or easy to note down. could rgb be used? 19:56:18 How would red/green/blue values be easier to remember than 4 words? 20:01:22 Words are easy to communicate across different media, and are easier to "self-checksum" than random characters 20:02:09 I don't consider being "memorable" to be a good criterion 20:26:36 The fun stuff is composite unicode glyphs, where multiple unicode chars come together as one. 20:26:47 That insanity is just weird. 20:43:40 fluffypony: "did you see the log I dropped in yesterday?" -> missed this one (found it in the logs, but the paste is not available now), could you re-upload it again? 21:06:36 any feedback on https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/138 ? 21:17:29 I would like it generally 21:19:05 it's not a large proposal, so not a big deal there, but there might be some concern about scope and communication (?) 21:21:12 Would be nice not to break api_wallet (libwallet/libwalletqt interface) 21:26:26 dsc_: don’t think they will touch it in this CCS 21:43:41 tbh atm I'd be ok with it even if the diffs were large, if it removes an obstacle to others to contribute. 21:44:13 As long as it doesn't go too much in the "because I like it better that way" direction as it often does. 21:44:57 I find it a bit irritating that he seemed to want a blank cheque though. Obviously it'll depend on what the end result is. 21:56:53 I guess first step would asking if he is still interested in this CCS as it is a couple months old. 22:12:28 I understand why new developers aren't well-received by the CCS, but I also find it a bit disheartening given the amount of talented reviewers and the escrow system 22:13:16 It does stop debates about milestone completion or lack-of due to quality issues though.