Skip to content

PKT-FullNode-v1.0.1

Latest
Latest
Compare
Choose a tag to compare
@cjdelisle cjdelisle released this 09 Jan 16:42
PKT-FullNode-v1.0.1
0cf96f8
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

PKT-FullNode v1.0.1

Jan 9, 2024

This is a minor update to the PKT-FullNode which addresses a number of bugs, but it constitutes the first full
release of PKT-FullNode. PKT-FullNode is a fork from
pktd-v1.6.1, a single repository with the
full node, wallet, and lightning daemon all in one. The purpose of this branch-off is to isolate changes to the
full node as these must go through a higher level of verification as any change which affects the consensus
logic may cause an accidental hard-fork of the chain.

Security

General updates

  • Removed all files which are not necessary in order to build the pktd full node
  • Update to golang v1.18

Improvements to ban logic

  • Reimplement ban manager to ban IP addresses rather than banning nodes. Banning nodes is ineffective because the node can simply disconnect and reconnect again.
  • Ban nodes if they connect and disconnect too quickly.

Improvements to peer connection logic

  • Added new seed nodes (seed.pkt.pink and seed.pkt.ai)
  • Collect local addresses and determine whether different remote addresses are reachable, for example, do not
    attempt to connect to a cjdns address unless you have cjdns, or Yggdrasil address, or IPv6 address, etc.
  • On startup, do not trust IP addresses received from other peers, only trust those which come from DNS seeds
    or those which we have already actually connected to before. Once we have at least 8 outgoing connections, we
    switch to "relaxed mode" and connect to any IP address we find, so as to test the ones that we learn about from
    other nodes.
  • Rewrite Address Manager, particularly GetAddress() so that it will never fail by chance. Rather than picking random peers and potentially failing, it picks a random starting point and walks until it finds a suitable candidate, however if there is even 1 peer that is suitable, that peer will be returned.
  • Do not tell other nodes about an IP we learned about until we have actually connected to it at least once.
  • Set default maximum incoming peer connections to 2048 which is commonly used in practice.

Checkpoints

Checkpoint up to block 2260992 (December 2nd, 2023)

Bug fixes

  • Improper use of locks in BanScore() makes "getpeerinfo" hang indefinitely
  • Json-iterator cannot serialize a map, causing "getblockchaininfo" to crash
  • "debuglevel" RPC was not implemented.
Assets 2
Loading