All templates

Automated Bitwave Audit Trail Completeness Check

Every Monday, WebRun opens Bitwave, reviews the audit trail for the rolling 90-day window and checks that every transaction has a classification, an on-chain transaction ID, a source wallet, and a timestamp. It posts a completeness report to Slack listing any gaps so your team can resolve them well before the next audit.

Runs on WebRun · Strict Lockdown policy
Every Monday at 9:00 AM WebRunorchestrates each step
1 Bitwave check audit trail completeness for the rolling 90-day window
2 Slack post audit trail completeness report
In short

How do I automatically verify my Bitwave audit trail is complete before an audit?

WebRun reviews your Bitwave audit trail every Monday for the rolling 90-day window, checks that every transaction has a valid on-chain transaction ID, classification, source wallet, and timestamp, and posts a completeness report to Slack. Your team sees the gap rate and top gap types and can resolve missing fields well before auditors request the records.

  • Audit trail gaps caught and reported weekly, not on audit day
  • Gap rate tracked over time so completeness improves each week
  • Auditors receive complete, traceable transaction records on request

Built for crypto controllers · Web3 audit teams · digital asset accountants · blockchain compliance officers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.bitwave.io in a real browser with your saved login - no setup, no API keys.

  2. 1
    Bitwave - check audit trail completeness for the rolling 90-day window
    bitwave.io
    WebRun in Bitwave: check audit trail completeness for the rolling 90-day window
    WebRun opens Bitwave to check audit trail completeness for the rolling 90-day window.
    • Open Bitwave and navigate to the Audit Trail or transaction history view
    • Filter to the rolling 90-day window (or the range you specify)
    • Check each transaction for a valid on-chain transaction ID, source wallet, classification, and timestamp
    • Count transactions missing any of the four required fields
    • Note the total transaction count, complete count, and gap count

    Done when All transactions in the audit window have been checked and gaps are counted.

  3. 2
    Slack - post audit trail completeness report
    slack.com
    WebRun in Slack: post audit trail completeness report
    WebRun opens Slack to post audit trail completeness report.
    • Post a completeness report to your accounting Slack channel
    • Show total transactions checked, count complete, count with gaps, and gap rate as a percentage
    • List the top five gap types (missing classification, missing TX ID, missing wallet, missing timestamp)
    • Link directly to the Bitwave audit trail filtered to the gap transactions

    Done when Your team has this week's audit trail completeness report in Slack.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.bitwave.io
ScheduleRuns automatically on this cadence
Every Monday at 9:00 AM
DeliveryHow each run's result reaches you
Audit trail report · Slack
OutputWhat each run produces - A weekly audit trail completeness report in Slack with gap counts, gap types, and a direct Bitwave link to the incomplete transactions.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it export or share the audit trail with auditors automatically?

No. WebRun checks completeness and posts the internal report to Slack. Any audit export or submission to a third party is prepared as a draft for your controller to review and approve before sharing.

What window does it check by default?

The rolling 90 days by default, which covers most audit lookback periods. You can change the window to match your audit engagement period during setup.

Can it check Bitwave's immutable log?

Yes. Bitwave maintains an immutable transaction log with timestamps and IDs. WebRun reads that log to verify each entry has the required fields and flags any that fall short.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.