[BBLU] Bitcoin-Blu

[nicovoss]

I think I can help with the development, but to do that I need to know what kind of development you want for the project. What changes you’d like compared to the original Bitcoin source code ?  Also, are the miners supporting the developers’ efforts in any way, for example, with Bitcoin Blue tokens?

Great, we really appreciate that.
There are two independent areas where you could help:
- writing a DNS seed server that finds running BBLU full-nodes
- writing a Ledger device app, where we can store BBLU
If you want to help with the bitcoin-blu-core, you can just clone the GitHub repo and send small pull-requests.
- e.g. fixing broken test cases

I don't want to make any promises, but in a community, efforts are usually rewarded. However, it is based on voluntary, unpaid work.
Would you like to join the Discord Server?: https://discord.gg/AHDrFavK
 

I don’t understand this development task, ‘writing a DNS seed server that finds running BBLU full nodes,’ since distributing the active nodes is a core function of the client. For example:

Code:

root@bitcoin_blu:/opt/workspace/orig# /opt/workspace/orig/bitcoin-blu/build/src/bitcoinblu-cli --datadir=/opt/workspace/bblu01 getpeerinfo | grep addr | grep 8343
    "addr": "139.59.206.162:8343",
    "addr": "209.38.28.44:8343",
    "addr": "170.64.246.225:8343",
    "addr": "143.198.42.66:8343",
    "addr": "83.44.88.143:8343",
root@bitcoin_blu:/opt/workspace/orig# 

[biblu]

I don’t understand this development task, ‘writing a DNS seed server that finds running BBLU full nodes,’ since distributing the active nodes is a core function of the client.

You're right!
DNS seed servers make the Bitcoin-Blu network more robust and decentralized.

Background: The following steps are performed by the Bitcoin-blu node on the startup to find peers:
1    peers.dat    Previously known peers (empty list on first startup)
2    DNS seeds    Determining the initial IPs
3    Hard-coded fallback seeds    Backup in case of DNS failure
4    Peer gossip (addr messages)    Determining additional nodes
5    Save to peers.dat    Later reuse

Why DNS seeds are needed
Hardcoded nodes go stale
- The hardcoded seed list (chainparamsseeds.h) is static — it’s compiled into the binary at release time.
- Those IPs represent a snapshot of reachable nodes months (or even years) old.
- Over time, many of those nodes go offline, change IPs, or shut down entirely.
- If Bitcoin-Blu Core relied only on those, a new user might fail to connect after the list decays.

A Bitcoin DNS seeder (like bitcoin-seeder by Pieter Wuille, or dnsseed by other maintainers) is a standalone lightweight server that continuously maps the live Bitcoin P2P network and exposes reachable node IPs through the DNS system.
Let’s go through the core software blocks and architecture step by step:

Bitcoin-Blu DNS seed is essentially a combination of:
- crawler → finds and tests Bitcoin-Blu nodes
- database → stores and scores known nodes
- DNS server → answers DNS queries with good node IPs

Does this explanation help you?

[nicovoss]

I don’t understand this development task, ‘writing a DNS seed server that finds running BBLU full nodes,’ since distributing the active nodes is a core function of the client.

You're right!
DNS seed servers make the Bitcoin-Blu network more robust and decentralized.

Background: The following steps are performed by the Bitcoin-blu node on the startup to find peers:
1    peers.dat    Previously known peers (empty list on first startup)
2    DNS seeds    Determining the initial IPs
3    Hard-coded fallback seeds    Backup in case of DNS failure
4    Peer gossip (addr messages)    Determining additional nodes
5    Save to peers.dat    Later reuse

Why DNS seeds are needed
Hardcoded nodes go stale
- The hardcoded seed list (chainparamsseeds.h) is static — it’s compiled into the binary at release time.
- Those IPs represent a snapshot of reachable nodes months (or even years) old.
- Over time, many of those nodes go offline, change IPs, or shut down entirely.
- If Bitcoin-Blu Core relied only on those, a new user might fail to connect after the list decays.

A Bitcoin DNS seeder (like bitcoin-seeder by Pieter Wuille, or dnsseed by other maintainers) is a standalone lightweight server that continuously maps the live Bitcoin P2P network and exposes reachable node IPs through the DNS system.
Let’s go through the core software blocks and architecture step by step:

Bitcoin-Blu DNS seed is essentially a combination of:
- crawler → finds and tests Bitcoin-Blu nodes
- database → stores and scores known nodes
- DNS server → answers DNS queries with good node IPs

Does this explanation help you?

If I’m understanding correctly, the GitHub repository you shared needs some changes to work with BitcoinBLU. The DNS server and the modified ‘poor-man’s’ node checker + databased will require a VPS. Is a spare VPS available for this task?

[biblu]

If I’m understanding correctly, the GitHub repository you shared needs some changes to work with BitcoinBLU. The DNS server and the modified ‘poor-man’s’ node checker + databased will require a VPS. Is a spare VPS available for this task?

Yes.
- The shared GitHub repository is just an example of a SED server implementation. Probably there are other examples.
- Yes, we need to clone and modify it for the Bitcoin-Blu blockchain.
- Yes, we will find a place to host the SED server.
- and we need to implement the address of the SED server in the bitcoin-blu-core code.

[nicovoss]

If I’m understanding correctly, the GitHub repository you shared needs some changes to work with BitcoinBLU. The DNS server and the modified ‘poor-man’s’ node checker + databased will require a VPS. Is a spare VPS available for this task?

Yes.
- The shared GitHub repository is just an example of a SED server implementation. Probably there are other examples.
- Yes, we need to clone and modify it for the Bitcoin-Blu blockchain.
- Yes, we will find a place to host the SED server.
- and we need to implement the address of the SED server in the bitcoin-blu-core code.

I’ve changed what I thought needed changing. Among other things, I updated the port, the pchMessageStart bytes, and the IP addresses. I’m looking forward any feedback. source code: https://github.com/nicovossdev/bblu-seeder

[biblu]

I’ve changed what I thought needed changing. Among other things, I updated the port, the pchMessageStart bytes, and the IP addresses. I’m looking forward any feedback. source code: https://github.com/nicovossdev/bblu-seeder

Great! 
I also created a channel on Discord for that topic: dev-dns-seed-server
Do you have access to Discord as well?

[nicovoss]

I’ve changed what I thought needed changing. Among other things, I updated the port, the pchMessageStart bytes, and the IP addresses. I’m looking forward any feedback. source code: https://github.com/nicovossdev/bblu-seeder

Great! 
I also created a channel on Discord for that topic: dev-dns-seed-server
Do you have access to Discord as well?

Discord eats up a lot of my time and isn’t really suitable for development. I’ll remain active here on Bitcointalk. Alternatively, feel free to open source-code–related issues on GitHub.

[biblu]

Discord eats up a lot of my time and isn’t really suitable for development. I’ll remain active here on Bitcointalk. Alternatively, feel free to open source-code–related issues on GitHub.

I have some compiling issues on ubuntu. I created a Issue: https://github.com/nicovossdev/bblu-seeder/issues/1
Did id compile on your site?

[nicovoss]

Discord eats up a lot of my time and isn’t really suitable for development. I’ll remain active here on Bitcointalk. Alternatively, feel free to open source-code–related issues on GitHub.

I have some compiling issues on ubuntu. I created a Issue: https://github.com/nicovossdev/bblu-seeder/issues/1
Did id compile on your site?

I built it on Debian 13 without any issues, but when I tried on Ubuntu it indeed failed to compile. I've fixed this bug.

[biblu]

I built it on Debian 13 without any issues, but when I tried on Ubuntu it indeed failed to compile. I've fixed this bug.

Great, it compiles!
I'll try to install the seed server.
Did you provide your bblu address in case anyone wants to support your work?

[biblu]

I built it on Debian 13 without any issues, but when I tried on Ubuntu it indeed failed to compile. I've fixed this bug.

It compiles.
Did it worked on your side? Did you get responses from the DNS? my log says:
[25-11-05 06:14:09] 0/69 available (69 tried in 171s, 0 new, 0 active), 0 banned; 0 DNS requests, 0 db queries
But I do not get DNS responses.
Any idea?

[nicovoss]

I built it on Debian 13 without any issues, but when I tried on Ubuntu it indeed failed to compile. I've fixed this bug.

It compiles.
Did it worked on your side? Did you get responses from the DNS? my log says:
[25-11-05 06:14:09] 0/69 available (69 tried in 171s, 0 new, 0 active), 0 banned; 0 DNS requests, 0 db queries
But I do not get DNS responses.
Any idea?

If there isn’t a proper DNS server configured that supports reverse lookups for at least one IP–hostname pair, then there’s nothing it can return.

[biblu]

  New BBLU mining pool here--- https://ugpool.lol/

[nicovoss]

Do you need help setting up a few nodes on addresses that can also be resolved via reverse DNS, and configuring the DNS seed server on one of them?
Reverse DNS means that you can get the domain name associated with an IP address from the IP itself.
In the case of Linode, there are very good step-by-step guides available online, so that’s what I’d recommend, as it’s the simplest way.

[biblu]

Do you need help setting up a few nodes on addresses that can also be resolved via reverse DNS, and configuring the DNS seed server on one of them?
Reverse DNS means that you can get the domain name associated with an IP address from the IP itself.
In the case of Linode, there are very good step-by-step guides available online, so that’s what I’d recommend, as it’s the simplest way.

Many thanks . I guess, I really need to dive deep into this topic. I try to run your code on a DigitalOcean Droplet. The service runs, but I think I messed it up  with the DNS configuration between domain controller and DigitalOcean or the Firewall (port 53 is open).

[nicovoss]

Do you need help setting up a few nodes on addresses that can also be resolved via reverse DNS, and configuring the DNS seed server on one of them?
Reverse DNS means that you can get the domain name associated with an IP address from the IP itself.
In the case of Linode, there are very good step-by-step guides available online, so that’s what I’d recommend, as it’s the simplest way.

Many thanks . I guess, I really need to dive deep into this topic. I try to run your code on a DigitalOcean Droplet. The service runs, but I think I messed it up  with the DNS configuration between domain controller and DigitalOcean or the Firewall (port 53 is open).

The DigitalOcean droplet is an excellent solution. It would be good to set up at least two of these, and then configure DNS resolution to the droplet’s IP. You can even set the A record directly where the domain name is hosted—for example, seed1.bitcoin-blu.com and seed2.bitcoin-blu.com. Have these subdomains point to the droplet’s IP address. Once these are in place, I’ll test the name resolution and update the code accordingly.