v0.1.19

• Suppliers: changing a supplier's stake or services now always keeps its owner and how its rewards are split, exactly as they are on the network. The app checks this itself before signing, so neither the app nor an assistant using it can hand a supplier to a different owner by mistake.
• Claude can now look over a server whose supplier was set up by hand, without changing anything on it: which RelayMiner runs there, the services it serves and their backends, what answers on the web ports, and which keyring or keys file holds the operator's key. No key is ever shown. This is the first step of importing such a supplier into the app.
• Suppliers: a custodial supplier, one whose operator is also its owner, can now be restaked from the app. The stake stays custodial: stake increases come from the operator account, and returned stake and rewards stay with it. Unstaking one from the app is not possible yet.
• Suppliers: a supplier set up by hand can now be imported into the app. Press Import next to it under "Suppliers set up outside this app". For a supplier staked with its operator as its own owner, enter its operator address under "Import a supplier by its operator address". The app looks over the server first and shows what it will do, and it will not start if something is in the way. Then it builds its own RelayMiner next to yours with the same operator key, finding the key on the server or taking it from you once, and points it at your existing backends. It stops new relays to yours and waits until your last claims are proved, then switches over. The stake, the owner, and the services on the network stay as they are. The import picks up where it left off if the app is closed partway through, and "Put theirs back" starts your own setup again.
• Provision and Deploy now work on a server where only the administrator can create folders under /opt, as on many servers set up by hand. The app creates its folders there with the server user's sudo and hands them to that user.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.19/CHANGELOG.md#0119

v0.1.18

• Provision a supplier: a new "Public port" box for a server behind a router that forwards another port to it (for example 8445). The supplier is staked at that port, so a supplier reached as https://host:8445 keeps working when the app stakes or restakes it. Leave it empty for the usual 443.
• Suppliers: if your owner wallet has suppliers that were set up outside this app, for example with pocketd on the command line, they are now listed under "Suppliers set up outside this app", with their services, address, and stake. The app cannot manage them yet; leave them running. Importing them is coming.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.18/CHANGELOG.md#0118

v0.1.17

• The app now tells you what happened. Copying an address, a token, or a recovery phrase shows a short "Copied to clipboard" message, also inside dialogs, where the bottom bar was hidden. Opening a link or a folder says it opened in your browser or File Explorer, or why it could not. Creating, importing, recovering, or removing a wallet, and approving or declining an assistant's request, say so where you are instead of only in the bottom bar.
• Refresh, Rescan, Re-check, Requery, and Test connection show a spinner while they work and cannot be pressed twice; then they briefly say "Updated" or show what went wrong, including when the network could not be reached. Check for updates says when you already have the latest version. Rescan says how many services it found.
• Deploy, Test, and Provision can no longer be started twice by a quick second click, and a step that fails part way now ends with its reason shown instead of leaving the app greyed out until a restart. The same holds for sending POKT, returning POKT to the owner, and the wallet and key dialogs, and for the Claude Integration buttons.
• Suppliers, supplier editor: Add adds the service the list shows without choosing it first, and the RelayMiner URL at the top now applies to every service below that has not been given its own.
• Importing from the older app: a folder chosen with Browse now shows in the box.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.17/CHANGELOG.md#0117

v0.1.16

• My services, Edit card: saving an edited card now writes it back to the folder it came from. Before, it went to a new folder named after the service ID, so a service whose folder had a different name ended up listed twice, with the edit in the new copy and no way to remove it from the app.
• My services shows one entry per service even when two folders say they are the same service. The entry uses the folder with the service's code in it and names the other folder, which can be deleted. Deploy and Test use that same folder.
• Create refuses a new service whose ID another folder already holds, and points to that folder's Edit card instead.
• My services reads the service folders again when it opens and when you press Refresh, so a folder added, changed, or deleted outside the app shows up without restarting it.
• Dashboard: the chain panel and the services table now keep themselves up to date while the Dashboard is open, about once a block. The block height and the "next session" countdown move, and a supply marked pending turns active when its block arrives, without leaving the screen and coming back. It pauses while the window is minimised.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.16/CHANGELOG.md#0116

v0.1.15

• Provision a supplier: setting up a new server no longer stops at "Operator public key on chain" after five minutes of waiting. The step had already worked; it was looking for the wrong word in the network's answer, so it never saw its own success. Running Provision again got past it, and now the first run does.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.15/CHANGELOG.md#0115

v0.1.14

• Deploy service: a service deployed without its own compose file now runs with a 512 MB memory limit, so one runaway service can no longer take the memory the supplier's RelayMiner was sized with. A service that needs more says so in its own deploy/docker-compose.yaml. The shared Caddy on each server gets a 256 MB limit the next time the server is provisioned.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.14/CHANGELOG.md#0114

v0.1.13

• Supplier servers: the RelayMiner now checks each relay before passing it to your service, instead of passing it first and holding the request and the answer in memory until the check is done. On a small server with several services that holding space could outgrow the memory the relayer is allowed, and a burst of traffic would restart it. Suppliers shows "stack update needed" once more for stacks updated with 0.1.12; Update stack applies it and keeps everything else.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.13/CHANGELOG.md#0113

v0.1.12

Priority update. The RelayMiner published its first versioned release, and supplier servers set up by earlier versions of the app can no longer start it: new servers fail at once, and existing ones fail the next time the RelayMiner is downloaded again. Update the app, then press Update stack on each supplier (Suppliers screen).

• Supplier servers run a fixed RelayMiner version (v0.1.0) instead of one that could change underneath the app, with Redis 8.10 set never to throw away relays that have not been claimed yet. The memory each part may use is worked out from the server's own memory, so a server needs at least 3 GB. Before anything restarts, the new version checks both of its configuration files; if either check fails, nothing changes and the app says why.
• Suppliers and Settings mark a server whose supplier stack is older than this version of the app with "stack update needed" and an Update stack button. Updating keeps the operator key, the services and the stake.
• Priority updates: a release marked as a priority shows a banner with an Install now button and opens the update dialog once each time the app starts, until it is installed. This is the first version that can show one, so this release itself arrives as an ordinary update.
• Your server now comes first. Register asks for a provisioned server before a new service goes on chain, with a link to set one up; tick "Someone else will run the supplier" if another operator will supply it. The Dashboard, the welcome message, and Help put setting up the server right after importing the owner wallet.
• Claude is told the same: the app's status tells an assistant to set up the server in the app when none is provisioned, and never to provision a server or stake a supplier on the command line, and the app refuses to register a new service for an assistant until a server exists.
• Provision a supplier no longer has its own network choice. It provisions for the network the app is on, and the stack folder and hostname follow the network switch, so a folder meant for one network can no longer be used for the other.
• Dashboard: the red box listing application stakes below their minimum is gone. It could not be dismissed and repeated the badge in the Margin column; the line under the badge now says what happens and what to do.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.12/CHANGELOG.md#0112

v0.1.11

• Deploy service: a service that keeps separate data for each network can say which port each network's RelayMiner calls, in deploy/relayer.json. Deploy connects the RelayMiner for the chosen network to that port and checks the service answers there, so Beta test traffic can never reach the MainNet copy. Services without the file keep using port 8080 on both networks. An extra address from deploy/routes.json can never point at one of these ports, since it would bypass the RelayMiner. A server provisioned by an earlier version needs Re-provision under Settings first; Deploy says so.
• Deploy service: deploying again now updates the RelayMiner's entry for the service when its port or its readiness check changed, instead of keeping the old one.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.11/CHANGELOG.md#0111

v0.1.10

• Test service: each probe is also timed against how long gateways wait. An answer that takes more than 10 seconds still passes but shows in yellow, since gateways set to 10 seconds will cut it off; one that takes more than 30 seconds fails, because no gateway waits that long. The time is the supplier's own round trip, not the few seconds the test spends starting up.

Every change, all versions: https://github.com/pokt-network/PSM4Win/blob/v0.1.10/CHANGELOG.md#0110