Skip to content

Conversation

@sipsorcery
Copy link
Contributor

As discussed in #1226.

#if !NOSOCKET
.AddSeeds(new[]
{
"178.128.221.177",
Copy link

@1ma 1ma Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These seeds are for the main signet, I don't think it's correct to include them on a custom one.

On a custom signet the seed node would be the IP of the block-emitting node, which could be anything (a public IP, a LAN IP, etc).

builder.SetChainName(name == DEFAULT_SIGNET_NAME ? SignetName : new ChainName(name));
builder.SetNetworkSet(this);
builder.SetConsensus(new Consensus()
{
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(GitHub doesn't allow me to comment on line 38 so I leave this comment here, the closest I could)

Bitcoin Knots supports -signetblocktime, which is a very useful flag for a custom signet. Maybe PowTargetSpacing could also be parameterized while keeping the default value of 10*60.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants