selsta_: did you get a chance to look at this?

joe-molested-hun: did you try to delete `~/.shared-ringdb/` as a workaround?

joe-molested-hun: did you try to delete `~/.shared-ringdb/` as a workaround?

my problem is that I'm not familiar at all with this ringdb thing and moneromooo (author) is currently not available

so I don't even know how it should work

I did not--would that not cause problems?

<selsta> "my problem is that I'm not..." <- I see. Bummer :(

Maybe I will dig deeper and try my hand at definitively identifying and fixing the root cause.

Since it is so difficult to register an anonymous GitHub account, it would be great if someone could do that for me. .05 XMR tip to the first person to send me login details for a GitHub account with working verified email address

joe-molested-hun: at which part did you get stuck (regarding github account)?

last time I created one only an email was required

Not any email is accepted, and most anonymous email providers either simply don't work (email is never sent) or remains "unverified" in the GitHub account so you cannot make issues, PRs, etc.

The idea behind the shared ring db as far as I understand it is to prevent you from respending an output with a different ring construction, which would reveal the real output spent (like on a fork for example)

Let's say a project Foo forks Monero and you now have Foocoin on Foo because you had Monero. When you spend your Foocoin, there will be a key image associated with your ring on Foo. When you spend the same Monero, you'll have the same key image but different ring members (except your real output). So someone can tell which output was spent in the ring because it would likely be the only one in common across both rings. The shared ring db

protects users from using different ring members across forks when spending the same output

Could be wrong but I think it's also useful if you submit a tx that doesn't broadcast because a malicious node withholds it. This would ensure you resend the same ring, so malicious node can't tell which output is real by cross referencing

Thanks a lot, that explains it very well

<jberman[m]> "Could be wrong but I think it'..." <- I wonder if this buggy behavior I experienced is actually related to some feature designed to protect against this scenario with a malicious node that refuses to broadcast the tx.

joe-molested-hun, tutanota, protonmail etc. didn't work? www.guerrillamail.com ?

Does the transaction size limit apply to the coinbase transaction as well? Sadly I could not figure it our by reading the code.

hqm42: I don't think so

I am asking in the context of p2pool... Is it possible to mine a block with thousands of outputs?

Right I remember. A coinbase tx can have unlimited outputs, while a normal tx can have at most 16 outputs.

'unlimited' so long as the block size cap is respected.

Cool. Thank you!

So currently I have about 250kb hard limit for the coinbase transaction before I have to throw out other transaction?

I think the max block size is 600kB, but if you exceed 300kB then there will be a block reward fee.

block reward penalty*

<gingeropolous> "joe-molested-hunter, tutanota..." <- I got protonmail to work eventually, thanks to @wfaressuissia

Thanks :)

Anyone on IRC? Let me know if you see my messages.

yes

luigi1111 messaged you several times but it keeps spitting the same message: user is not online or doesn't exist.

hmm dunno about that

ok pm me when you have time, want to get my M2

escapethe3ra: I think you asked luigi1111w rather than luigi1111

Rucknium[m]: nah, tried both

I'm away till Tuesday, is that ok or you need it sooner?

luigi1111: Tuesday

* Tuesday's fine, no rush

thanks I'll write it down :)

hey folks, hope you're well. i'm not sure if you all have come across our activities so i wanted to introduce myself. It would be great if we could call upon the experience in this chat in the future for technical questions. bounties.monero.social/posts/31/monero-guides-mini-series

currently I need some help with some wording. 'When you connect to remote nodes which are not owned by you, it is possible for the host to obtain your IP address, along with information which is accessed and transmitted.' i think it's important to be clear and specific and 'along with information which is accessed and transmitted.' isn't really fitting the bill. Can i have some recommendations?

s/some//

<monero-guides[m]> "currently I need some help..." <- Remotes Nodes can see X ip has started syncing from 1234 block and abcd…z tx is being broadcasted

So the remote node can see the TXID. Can it see any info about decoys?

anarkiocrypto[m]: Not sure, some Dev can shine some light on this if decoys are been sent by remote nodes or wallets select them while scanning the blockchain