Stratum V2 is live on both lanes

PotPool now speaks Stratum V2. Every port you already use keeps working exactly as before, and each lane has a V2 port next to it: the V1 port plus 100.

SHA-256d  stratum2+tcp://sha256.potpool.party:3433
Scrypt    stratum2+tcp://scrypt.potpool.party:3434
Key       9bo4JzAJCKuWRbquhFMYHtFea34jtQQz287iiXEw9humw1KGQvd

Your username is the same as on V1: 0xYourBaseAddress.rig1. Shares from V1 and V2 rigs under one address are added together on your miner page, and a share is worth exactly the same on either protocol.

What V2 gets you

Encryption. V1 sends everything in plain text, so anyone on the path between your miner and the pool can read it or quietly point your hashrate somewhere else. V2 encrypts the connection, and your miner checks the pool's key before it sends a single share. That is what the key above is for: it proves the miner is talking to PotPool and not to something in the middle.

Smaller messages. V2 is binary instead of JSON, and a new block only needs a tiny message once the job is already on your miner.

Setting it up in AxeOS (Bitaxe)

1. Open Pool settings and switch the protocol to Stratum V2.
2. Host sha256.potpool.party, port 3433.
3. Paste the key above into the authority key field.
4. User 0xYourBaseAddress.rig1. Leave the channel type on Extended, which is the default.

Other V2 firmware works the same way: host, port, user, and the key. If your firmware wants it all in one URL, use stratum2+tcp://sha256.potpool.party:3433/ followed by the key. The setup generator has copy buttons for all of it.

I tested the V2 endpoint against the reference implementation's translator proxy, with real blocks found and accepted by the DigiByte node, and my own Bitaxe Gamma now mines on V2 with zero rejected shares. If your device does something odd on V2, tell me, and point it back at port 3333 in the meantime.

What it doesn't do (yet)

• Extended channels only. That is what AxeOS and the reference translator use by default. The older "standard" channel mode is refused with a clear error.
• Rental rigs. Marketplace rigs that need a large extranonce (7 bytes or more) can't fit through an aggregating V2 translator. Keep them on V1, which is unchanged.
• Scrypt V2. The port is there, but I don't know of any Scrypt firmware that speaks V2 today. It is ready for when one does.

New blocks now reach you in milliseconds

This part helps everyone, on V1 too. DigiByte finds a block about every 15 seconds, and until today the pool only checked for a new one every couple of seconds. Your miner kept working on an old block for up to a few seconds each time, and that work could never win.

The pool now hears about a new block the instant the node does and sends fresh work straight away. In my tests the gap went from about a second on average, and up to four, to a few milliseconds. More of your hashrate now goes toward blocks that can actually be found, and that means more tickets for the pot.