To ease the transition to BIP148 and to minimise risks in the event minerschoose to perform a chain split attack, at least Bitcoin Knots will be usingthe temporary service bit (1 << 27) to indicate BIP148 support.

Once the transition is complete, this will no longer be necessary, and the bitwill be (manually) returned for reuse.

I encourage other software implementing BIP148 (both full and light nodes) toset and use this service bit to avoid network partitioning risks.

Post by Luke Dashjr via bitcoin-devTo ease the transition to BIP148 and to minimise risks in the event minerschoose to perform a chain split attack, at least Bitcoin Knots will beusing the temporary service bit (1 << 27) to indicate BIP148 support.Once the transition is complete, this will no longer be necessary, and thebit will be (manually) returned for reuse.I encourage other software implementing BIP148 (both full and light nodes)to set and use this service bit to avoid network partitioning risks.

I'm curious what you action on the finding (or not) of a peer with this bitset (or not).Can you link to the github commit where you implemented this?

Post by Luke Dashjr via bitcoin-devTo ease the transition to BIP148 and to minimise risks in the event minerschoose to perform a chain split attack, at least Bitcoin Knots will beusing the temporary service bit (1 << 27) to indicate BIP148 support.Once the transition is complete, this will no longer be necessary, and thebit will be (manually) returned for reuse.I encourage other software implementing BIP148 (both full and light nodes)to set and use this service bit to avoid network partitioning risks.

I'm curious what you action on the finding (or not) of a peer with this bitset (or not).Can you link to the github commit where you implemented this?--Tom ZanderBlog: https://zander.github.ioVlog: https://vimeo.com/channels/tomscryptochannel_______________________________________________bitcoin-dev mailing listhttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev