processor-1.29.0

Processor 1.29.0

version code: 144

Release Notes

UI

• Processor Lite now connects to Acurast Hub by scanning QR codes, replacing the Beacon browser connection.
• Paste from clipboard is back in onboarding QR scanning, and the scanning screens now scroll.

Signing

• Signing requests from Acurast Hub are decoded and checked before you sign. The app shows the action with its arguments, the account, the network and the runtime version, and warns when something does not match.
• Requests for a different account or network, and requests that contain only encoded transaction data, can no longer be signed.
• Messages that contain hidden or direction-changing characters are shown as hex, so they cannot read differently from what gets signed.

Deployments

• The Node.js runtime is updated to v24.22.1.
• Browser's DevTools is now served through an HTTP gateway instead of a raw relay. Connections close after each response, and the gateway answers 503 when too many are open at once.
• UDP egress is metered per destination instead of per datagram.
• Tunnels accept an optional reconnect budget.
• Cargo deployments can reset their own container, either by exiting the entrypoint with a resetExitCode declared in the manifest or by calling the new container_reset RPC method. A reset puts the rootfs back to its image and runs the entrypoint again within the same execution.
• Cargo deployments can get the processor's SS58 address and public key from the new processor_identity RPC method.

Bug fixes

• An error thrown from a timer or an immediate that the deployment does not handle no longer crashes the processor.
• Fixed resource leaks in the execution runtimes and the browser.
• Security patches for the execution runtimes and the browser.