Skip to content

Separate peers.ini for block #1 full sync #27

@sunburntcat

Description

@sunburntcat

With rise of producer api snapshots for fast replays, only a handful of peers actually have the entire chain available from block #1 on Mainnet and Testnet. A custom peer list would be helpful for all Telos nodes fast re-sync as nodes upgrade to Mandel.

The following are the beginning of a list of current known p2p nodes with full blocks.log at their disposal. Of course node operators may also already have their own internal seed nodes.

Telos Mainnet seed peers:
p2p-peer-address = p2p.telosunlimited.io:9876
p2p-peer-address = p2p.dailytelos.net:9876
p2p-peer-address = seed.telosmadrid.io:9876

Telos Testnet seed peers:
p2p-peer-address=telostest.seed.eosnation.io:9876
p2p-peer-address=seed-testnet.telosmadrid.io:9886
p2p-peer-address=p2p.testnet.telosunlimited.io:9876
p2p-peer-address=telos.testnet.boid.animus.is:3535
p2p-peer-address=telos.testnet.boid.animus.is:5050

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions