13:21:05 Monerujo app states my Node connection failed and Username/password is wrong 13:21:06 But all details are correct 13:21:06 What should I do? 13:21:52 I am unable to access the wallet 13:23:05 This isn't the right place for that, try #monero:monero.social or their subreddit (https://www.reddit.com/r/Monerujo/) or email them (help⊙mi) 13:24:52 Thank you 14:05:36 is there a reason the monero docs are a 'work in progress'? 14:15:20 What docs say that? 14:16:11 https://monerodocs.org/ 14:17:03 They are unofficial as clearly stated, so you should probably reach out to the author. 14:20:52 will do, thanks! 15:18:08 .merges 15:18:08 Merge queue empty 17:50:42 I am adding the ability to stash 32 bytes of hidden data in BP+. That data can be retrieved only by the sender. Do we want to store, eg, the tx secret key there, or something else, or leave that to the user ? 17:51:40 (32 bytes per tx) 17:53:58 why not leave it to the user? 18:03:44 oh I thought the recipient could retrieve that data too 18:04:31 * moneromoooo too 18:15:05 There is only one 32 byte value per tx, is it extra data when there is 1 non-change recipient? 18:15:27 Can you expand on "is it extra data" ? 18:16:12 If you mean "does it go into extra", then no. It's in the bulletproof data. 18:19:28 Also, later on, there will also be 32 bytes in the triptych proof, which can be retrieved by the recipient. 18:29:22 .merge+ 7825 7822 7821 7818 7817 7810 7809 7805 7802 7801 7800 7799 7798 7790 7791 7794 7788 7787 7796 7777 7747 7757 18:29:22 Added 18:29:52 moneromoooo: could you approve 7767? you approved it previously before rebase 18:31:12 Sure, not too large, I'll do it now. 18:33:47 Had to open a new PR because the author stopped replying. 18:33:50 Extra data as in... additional data a recipient can read. Transactions can have more than 1 recipient. 18:35:03 done 18:35:46 Well, there'll be some in triptych later which a recipient can read (one per tx). The one I'm doing now with BP+ won't. 18:36:26 If you want to add 32 bytes for every recipient, then I guess you can use extra, yes. But it's unrelated really. 18:38:05 do lelantus3 and seraphis support embedding such data? 18:39:11 Might not make sense to implement if it won't be possible in the future 18:39:17 I asked sarang that and the reply was "I think so". 18:40:04 (paraphrased, despite the quotes) 18:40:15 Groth/Bootle-type parallel proofs should support the same type of embedding as Triptych 18:40:26 moneromoooo: updated, not sure if that's the place to init them 18:40:34 shouldn't matter I guess 18:41:01 It's where I'd have done it. 18:46:03 Also, it's got the same problem as encrypted payment ids: you don't know whether what you get was put there by the sender or whether it's pseudo random data. 19:17:42 boogerlad[m]: message not going through, but that's not something that seems personal. 19:22:37 oh, is the libera <-> matrix bridge broken again? 19:23:20 no 19:23:23 No, it wants me to log in. Can't be arsed spinning the vault vm. 19:24:06 And you'll have better feedback posting in public. 19:24:45 fair enough. Do you think it's best to post in "monero dev", "monero", or reddit? 19:25:13 None of these seem off topic. 19:50:29 .merge+ 7767 19:50:29 Added 20:04:31 ArticMine binaryFate luigi1111w Is fluffypony's access revoked from everything? 20:04:56 is the general fund safe, etc 20:05:03 sgp_[m]: Good point -- any infra he has access too as well as Github etc. 20:05:06 Near enough but we're on it 20:05:21 okay thanks 20:11:16 the devices he had could have has malware installed for the past several weeks 20:12:03 sgp_[m] what makes you think that? 20:12:24 because he was arrested and his devices were confiscated 20:12:28 (I assume) 20:12:43 so who knows what people did with them 20:13:15 assume the worst 20:13:48 that all servers he had access to are compromised 20:13:59 Yes 20:14:10 And could have been before arrest, potentially. 20:14:14 He was arrested on the 21st. No devices were taken from him. His phone laptop etc are with someone else. 20:14:29 Oh great 20:14:51 binaryFate: Glad there has been other comms, should have expected that. 20:15:09 Anyway we're revoking accesses but I wouldn't overly worry about Monero specific infra. 20:15:36 How affected would MyMonero infra be? 20:15:48 he had no devices on the plane? 20:15:51 That could be massive honeypot if viewkeys were exposed/confiscated. 20:16:09 To be clear, yes we're assuming the worst and acting as if. But I see no reason to believe there was anything before that date. 20:18:16 he had no devices on the plane? <-- they were not confiscated as I've been told by the person having them. I think extraditions treaties are just about individuals anyway, not their posessions. 20:21:31 Wouldn't the devices be encrypted anyway? I would hope so. 20:22:17 Hope so but don't want to assume that. 20:22:18 Better to presume keys/creds are compromised and re-provision later as needed. 20:33:59 Wouldn't the devices be encrypted anyway? I would hope so. <-- they almost certainly would, so compromised access would also imply active willingness 20:59:04 .merges 20:59:04 -xmr-pr- 7747 7757 7767 7777 7787 7788 7790 7791 7794 7796 7798 7799 7800 7801 7802 7805 7809 7810 7817 7818 7821 7822 7825 20:59:09 luigi1111w: do you have time today? 20:59:31 .merge- 7825 20:59:32 Removed 20:59:38 wait when did this happen 21:03:02 If you mean Riccardo, quoting the cointelegraph article: "An arrest warrant for Riccardo Spagni was issued on July 20, 2021, at the request of the South African government. He was apprehended the same day in the United States." 21:06:40 spackle[m]: Has anyone been in touch with him since his arrest ? 21:28:24 his wife https://twitter.com/Spatzipantz/status/1422304460278276096 21:31:53 hyc: 👍 21:46:46 not like he could not have been picked up AT HOME a bunch of times between 2011 and now 21:47:44 * moneromoooo points to #monero 21:56:24 Are there any examples of unit tests that write/read from file (eg a wallet file)? 21:56:42 Yes, serialization. 22:11:54 Note that we temporarily removed fluffypony's admin rights from github Monero organization and all relevant repos 22:28:42 thanks 22:37:18 for what it's worth i was cut out from mymonero through a series of completely improper events 22:37:24 but i still maintain significant ownership 22:37:31 managed to hold onto it 22:37:46 i should be handed control of the servers in good faith by his attorney 22:37:51 i stewarded them for years 22:38:04 anyway we're building significantly better infra 22:38:07 among other things 22:38:11 so i'm not worried about it 22:38:36 i also dont really care for the inappropriately/unnecesarily massive monthly hosting bill 22:38:45 where there's smoke there's "fire" y'all 22:38:48 tried to tell you 22:38:56 but my personal safety came under threat 22:39:07 as well as my mental stability due to all kinds of gaslighting etc 22:39:41 let's all continue in #monero please 22:39:48 fair 22:40:01 cant say much rn anyway 22:40:11 oh oops i'm not in #monero 22:57:33 are we going ahead with 7798/99 ? 23:05:26 afaik yes because we have to merge 7821 23:06:02 so we want to include all changes to tx uniformity in one release 23:06:23 I was planning to include more detailed figures on tx uniformity impact there within the next 8 hours 23:06:23 An additional hesitation I have with it as is, is that it would cause the decoy selection algo to select more recent outputs today, but if the gamma shape from the paper is off in the direction I seem to have found (19.54 observed versus 19.28 in the paper), then it means the decoy selection algo is slightly biasing too recent today anyway. I'm still working on confirming the correct gamma shape separately 23:07:17 luigi1111: let's wait then 23:07:48 k