.merge+ 7278

Added

.merges

Goood Morning Vietnam! I think everyone here knows that most Monero exchange withdrawals and desposits are traceable (Breaking Monero poisoned outputs). How does it feel to go out and lie to people that they are private and then earn less than holding BTC on your bag?

So, my syncing stagenet node ends up banning all its peers and my node gets disconnected from the network all the time. I have huge logs after running with set_log 1. What should i grep for? Tried with "banned" and "blocked", but i didn't really find anything useful (except for "banned IP for N seconds)

on a side note, would be useful to be able to add multiple IPs to the 'unban' command. Like `unban IP IP1 IP2`, so that people don't have to type `unban IP` `unban IP1`, etc

dropping\ connection$

after restarting the node, it bans all the addresse and doesn't sync. ok will look for that

2021-01-03 16:17:56.993 [P2P6] INFO net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:2114 [159.69.121.11:38080 OUT] [0] state: resuming in state synchronizing

2021-01-03 16:17:56.993 [P2P6] INFO net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:2332 [159.69.121.11:38080 OUT] [0] state: We can download nothing from this peer, dropping in state synchronizing

2021-01-03 16:17:56.993 [P2P6] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1672 [159.69.121.11:38080 OUT] Failed to request missing objects, dropping connection

moneromooo ^

~1k lines before that, and to a paste site which is not centos.org.

moneromooo: paste.debian.net/hidden/9dc98918

i'm also seeing a few of `Got NOTIFY_RESPONSE_CHAIN_ENTRY past expected height, dropping connection`

wackadoodle idea for no port forwarding problem. might run into issues with attacks. If a node is providing blocks to a new node, it can add that node to its peer lists, and then send that peer list to its peers. The peers can see that a new node is trying to sync, and add it to its peer list via an outgoing connection.

seems the attacker comes at my node every 2 hours 12 min

Any short term solution (like a PR to try out) i could try to manage to sync that stagenet node? I really need it up asap.

logs from node restart until first bans: paste.debian.net/hidden/bc7a856e

Looks like these peers are very slow. Or you are. So they timeout.

You can bump a couple timeouts:

Even easier: comnent this line out: m_idle_peer_kicker.do_call(boost::bind(&t_cryptonote_protocol_handler<t_core>::kick_idle_peers, this));

mmh. Now it could definitely be me having a slow connection, but it also happened few days ago, when i had decent internet. Anyway. Thanks mooo.

Are there any plans to support 14 word mnemonic seeds on the official GUI wallet?

It would be less likely for users to mess up their backups of the key, and will also include the blockheight of the wallet creation so users don't have to restore from block 1.

Yes, it's planned, but no specific ETA yet

Awesome

does the cli wallet support those 14 word seeds?

Not yet

is somebody currently working on this or not rn?

Feather wallet uses 14 word seeds

The code can easily be ported

oh cool ill look into it

thnx!

What kind of person runs scams in their own community?reddit.com/r/Monero/comments/6d5yt5…/what_fluffypony_just_did_is_not_ok Your own leaders are laughing at how stupid you are for falling for thier 'Magical Crypto Friendship'.

jess: You are required urgently to save fluffypony's honour ^^

jess: ^ :)

klined already

thxi

monero-project/monero #7283 Yet another one, that does no harm, to say the least. Tests execute 20% faster thanks to parallelism.

.merge+ 7266 7267

Added

What kind of person runs scams in their own community?reddit.com/r/Monero/comments/6d5yt5…/what_fluffypony_just_did_is_not_ok Your own leaders are laughing at how stupid you are for falling for thier 'Magical Crypto Friendship'.

Has anyone ever worked on an independent implementation of Monero?

I remember posting some of my work here months ago and this came up.

I think it was moneromooo that said they wished another node impl existed? Just to check against by having another point of reference?

*Clarifying why it'd be beneficial not only to say the point wouldn't be to replace the existing node, but also because someone asked why bother.

This would probably cause forks all over the place. What I'd like is a... verifier, I guess. Something you can run offline-ish. And if there's a discrepancy, you look into it.

I mean, I'm not suggesting deploying it :P Just curious if anyone ever did this work

That said, no, it wouldn't probably cause forks. The lack of specification of the protocol is likely to leave edge cases hanging, of course, but multiple cryptocurrencies have multiple codebases without issue.

Even BTC has proper alt node impls, even with its utter lack of official protocol documentation + requirement on bug for bug compat which is bs.

Anyways. If someone put in the work on a block processor/TX verifier/so on, it could be turned into a verifier or turned into a node.

I remember reading about at least one such fork with... I think it was ethereum.

I guess if it's just one it's not too bad in the grand scheme of things, but stil, it's definitely possible, and I say probable.

I remember recently Infura died. I think that came with a netsplit of Geth/Parity? Not sure. That said, a single split over 6 years isn't "all over the place".

Oh. Probable for sure.

Not to mention Ed25519 malleability.

*I know Monero doesn't use EdDSA. I was referring to the TE variant of Curve25519.

Extremely easy to cause a netsplit with when multiple codebases exist.

Not sure Monero's rules on normalization. I did hear that in the past there was a double spend issue thanks to the torsion points though.

*thanks to the cofactor.

Anyways. Sound like no work on this exists?

I mean, I know there are wallets other than wallet2. Last I checked, there's only the one libringct (using MLSAG). SPV clients exist, yet they don't check bodies/TX validity. Just if they can spend a TX...

... though I think there's a Python prototype of CLSAG/the one before that.