Hi everyone, my name is (not sure if I should give my name or not). I am new to the monero dev community!  I have been interested in cryptocurrency since 2010, though only following it and using it sporadically.  I have also been aware of and interested in monero and other privacy coins for a long time, but in the spring I took a computer coding

bootcamp and I have decided to turn toward learning about cryptocurrencies on a deeper and more technical level.  I strongly believe in the mission of these coins, of which monero is of course the biggest.  So, I'm interested in learning more about it on a technical level and contributing to the project!  I have already read the book Mastering

Monero.  Where should I turn next?

(this is also my first time using IRC)

My bootcamp, btw, was about web development so we learned javascript.  But it kind of broke the ice for me on getting into a lot more of this tech, so I know I'll need to start using C++ for monero.  I've also been finding that I'm more interested in software engineering type problems than web development, so I have started learning more computer

sciency stuff, like doing leetcode problems

You don't need a name, there are many anon devs hear, but a proper handle would be useful.

The core monero codebase is quite complicated and messy, so its common that new people work on their own monero related side projects first. The right place for that is Monero Community Dev

<Guest25> "Hi everyone, my name is (not..." <- Hey, welcome to the community! What about joining us to help build golang library for Monero so you can get better understanding of how it works? The repo is located at: github.com/openmonero/monero.go

Thanks, will do for both of those!

hi guys, I'm not sure if I'm doing something wrong. But I just created a new watch-only wallet, did offline signing on another pc, then did the "submit_transfer" on the watch only wallet. it was send correctly but here's the issue: when I do "get_tx_key" on the watch-only wallet, I get this as a result: Tx key: 0100000000000000000000000000000000000000000000000000000000000000

which is weird, no?

It's NOT the real tx_key, I don't have any clue on how to extract it

it's not a big issue for me personally, but if people need to prove stuff for regulation purposes, this could become an issue

Hi, I think I am reproducing a bug in monerod on macOS/arm64. I had a node database I had synced a couple of years ago with prune-blockchain=1 that I was trying to get back up to date, but monerod was segfaulting at various points, and then is not able to proceed past a point about 3.3 months ago without segfaulting immediately when trying to sync. I tried a few different recovery steps that I found

online without success, and then decided to archive that database and try a brand new sync from scratch, also with prune-blockchain=1. This sync appears to be able to get to the same point, but then segfaults also. So I now have two databases which I can switch between, and monerod segfaults on both immediately upon trying to sync beyond 3.3 months ago.

here is a crash report: paste.debian.net/hidden/cdbaab0d

Following along with reddit.com/r/monerosupport/comments/w4iihg/segmentation_fault_11, I think I may have gotten past the problem block with MONERO_RANDOMX_UMASK=8, but that post is a year old and I know this issue is present on builds within the last 4-5 months

nick__: is it custom compiled? or from homebrew?

it's the basic homebrew install

see monero-project/monero #8829#issuecomment-1518932102

thanks!