v0.7.1

New Feature: DevTools file uploads

• _DEVTOOLS_.uploadFile() global — when devtools are enabled, processor scripts can now upload files to the DevTools API directly from the runtime. The injected snippet exposes a new _DEVTOOLS_ global with an uploadFile(filename, content, mimeType, onSuccess, onError) method that POSTs to /v1/files using fetch + FormData and the deployment's authenticated Bearer token. Files up to 10 MB are supported and the response includes { id, filename, mimeType, fileSize, createdAt }.

Improvements

• DevTools: removed __DEVTOOLS_DEPLOYER__ placeholder — the injected devtools snippet no longer requires the deployer address. The deployerAddress parameter has been removed from injectDevtoolsSnippet.
• DevTools: warn when used with IPFS URLs — enabling devtools with an ipfs:// file URL now logs a warning, since the snippet can only be injected into local bundles.
• Execution time validation warning — when maxExecutionTimeInMs is set to within 10 seconds of intervalInMs, the CLI now emits a warning instead of blocking deployment. This helps prevent executions from overlapping without being overly restrictive.

Documentation

• Added enableDevtools to the example config and configuration reference in the README.
• Added maxExecutionTimeInMs to the interval execution type documentation.

Full Changelog: v0.7.0...v0.7.1

v0.7.0

New Feature: Acurast DevTools Integration

The CLI now supports forwarding console logs from processor executions to the Acurast DevTools dashboard, giving developers real-time visibility into their deployments.

How it works

1. Add "enableDevtools": true to your project config in acurast.json.
2. Deploy as usual with acurast deploy <project>.
3. The CLI prints a DevTools URL with a view key after deployment completes.
4. Open the URL to see live console.log, console.warn, console.error, console.info, and console.debug output from your processors.

What happens under the hood

• At deploy time, a small snippet is prepended to your script's entrypoint inside the deployment bundle.
• On the processor, the snippet authenticates with the DevTools API using the deployment's ed25519 key (_STD_.signers.ed25519.sign) and obtains a scoped Bearer token.
• All console.* calls are intercepted, forwarded to the DevTools API, and still printed to the processor's local console.
• Logs are buffered during the brief authentication handshake and flushed once the token is obtained.
• A rate limiter (20 logs per 10 seconds) prevents runaway scripts from overwhelming the API.

Configuration

{
  "projectName": "my-project",
  "fileUrl": "dist/bundle.js",
  "enableDevtools": true,
  ...
}

Environment Variable	Default	Description
ACURAST_DEVTOOLS_URL	https://devtools.acurast.com	DevTools frontend URL used in the link printed after deployment
ACURAST_DEVTOOLS_API_URL	https://api.devtools.acurast.com	DevTools API URL used by the injected snippet and the CLI

Privacy

Logs are not publicly accessible. After deployment, the CLI requests a view key — a time-limited token scoped to the specific deployment. The DevTools URL printed by the CLI includes this view key as a query parameter. Only someone with the view key can read the logs. If the key expires, a new one can be requested by the deployment owner using acurast devtools <deployment-id>.

New Command: acurast devtools <deployment-id>

Request a fresh DevTools view key for an existing deployment. Useful when a previously issued view key has expired.

acurast devtools <deployment-id>

Outputs a DevTools URL with a new view key and its expiration date.

Full Changelog: v0.6.0...v0.7.0

v0.6.0

What's Changed

• feat: add dynamic pricing support

Full Changelog: v0.5.0...v0.6.0

v0.5.0

What's Changed

• Added support for mainnet

Full Changelog: v0.4.3...v0.5.0

v0.4.1

What's Changed

• Added a new command for fee-estimation. Run acurast estimate-fee and it will suggest a fee and compare it with your deployment configuration.

Full Changelog: v0.4.0...v0.4.1

v0.4.0

What's Changed

• Added support for upgradeable deployments. This advanced feature allows deployments to be created that are mutable, so they can be changed later on and keys can be re-used. This is an advanced feature and should only be used when necessary.

Full Changelog: v0.3.4...v0.4.0

v0.3.4

Fixes

• Listen to new event type when registering deployment

Full Changelog: v0.3.3...v0.3.4

v0.3.3

What's Changed

• Updated dependencies

Full Changelog: v0.3.2...v0.3.3

v0.3.2

What's Changed

• Rename console to hub
• Show assigned processors in acurast deployments <id> command

Full Changelog: v0.3.1...v0.3.2

v0.3.1

What's Changed

• Validate "required modules", now supports DataEncryption and LLM

Full Changelog: v0.3.0...v0.3.1