Topic: New IRC bootstrapping using random channels. - page 3. (Read 5618 times)

My idea: People still log into the IRC channel as now (so many in the community are so against centralization that they might wish to keep using this for bootstrapping connections, and they have every right to that) and then the DNS Seeds use the list from IRC to check which IPs accept incoming connections.  They keep a list and serve DNS records from that list.  That way DNS Seeds always have the most up-to-date list of nodes accepting incoming connections to give out to new clients.

How would one publish his availably to a DNS record then?

Very true.  DNSSeed is a much more appealing option, and there are some cool potentials there for faster startup as well.

IRC isn't a sustainable discovery protocol anyway. It has lots of problems beyond startup time.

This would be even better!

IRC will be fine, people just need to update faster. Need something like update notice in about window?

It'll take a long time for people to move across to the new channels. We might as well just switch to DNS instead.

Maybe laszlo can set it up so that no one can be an op in those channels.

Great! I got 25-49, and 50-74.

I would ask you guys to de-OP yourself, and not become OP again.

I've got 00-24.

Ok, so easy fix...people who won't break the chans join now until they have a ton of nodes in them, Ive got 75-99, someone want to grab the rest?

Currently there are 10,000 Bitcoin clients on the IRC server, in the main channel. Since you don't need to see all clients quit/join or get a 10k client list there is now the new system called 'split channel'.
This means a client will not join #bitcoin, but it will join #bitcoinxx, where xx is a random number between 00 and 99.
It is a great idea and will cut down bandwidth usage a lot for the server and the client!

There is one (major) downside for this.

What if an attacker would make bots join #bitcoin00 till #bitcoin99, and has OP (@) in all channels? He could lock the channel with a limit of one (+l 1), set a key (+k ywebnxs), or he could even ban everyone (+b *!*@*).

This would not work if all the channels would already have people in them, since OP would only be given once to the first one joining.
At the moment there are only 6 clients in the #bitcoinxx channels, so it's vulnerable and could be exploited any moment.

Possible fix: get some sort of IRC module/script to take control over these channels before an attacker does. This could either by joining the channel and let it de-OP itself, or never give OP in a #bitcoinxx channel.


Not fully working but to give you an idea, here is a bit of python script...


I see you guys found a quick fix: Join channels manually and de-OP yourself there.