Skip to content

v0.7.0

Choose a tag to compare

@AndreasGassmann AndreasGassmann released this 09 Apr 11:40
· 55 commits to main since this release
v0.7.0
33a3ff1

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