v0.27.3
최신A new install no longer starts by dialling a pool that is switched off. The default pool was Byron Bay, and Byron Bay is not answering: measured on 15 September from the reference rig and confirmed through a second network, its host drops every packet on all fourteen ports we tried and its own site returns "Byron Pool is paused". A fresh install printed that on screen while sitting on it. The default is now BTX Pool, and Byron leaves the automatic failover chain by the same rule that removed minebtx — it is dead, not dear.
BTX Pool is not the biggest pool; it is the only one an open client can reach. Of the two pools mining almost all of BTX today, one publishes no address for BTX at all and the other refuses every handshake an open miner can construct. If you already chose Byron yourself, easyBTX keeps your choice and still reaches the live pool behind it, so nothing you picked is overridden.
A pool address can now carry ssl://. easyBTX previously could not even save
one — the validator read the whole value as host:port and rejected the scheme —
so a TLS-only pool was unreachable by construction. It is accepted now, on the
platforms where the MATADOR engine is the client. This does not add a new pool; it
removes our side of the obstacle, so adding one later is a one-line change.
The retired-engine message stops naming a block height it invented. A pre-Ampere card with no Classic build was told "Classic is retired from block 185000" with the number written into the sentence, while the message beside it read the real activation height from the chain rules. They agreed only by coincidence. Both read it from the same place now.
Nothing else changed. Same mining path, same pinned solver, same census, same chain pins.