Plutonus

Active product 01 / Public Beta

Built by Plutonus · Live on Base Sepolia

Runrail

Submitting work is not the same as knowing what happened.

Each recurring job produces scheduled runs. Runrail follows each one through a limited number of attempts, records the result and keeps the available evidence together. Plutonus designed and built the product, from its execution logic to the App, API and public documentation.

Execution evidence 02 / Two recorded runs

One run reached the chain. One stopped safely before submission.

One reached the chain and was confirmed. The other stopped before a transaction was submitted. Both were recorded on Base Sepolia at separate scheduled times using the execution model now running in the Public Beta.

Recorded Base Sepolia run

Confirmed

Final outcome
Scheduled for
Network
Base Sepolia
Confirmed block
46173011
Transaction on BaseScan
0x4914ccb93a134917f510f18a621b7213a4d5b4a009e4ccf7048a1e151a1f437c
outcome
CONFIRMED
chain_id
84532
externalization_count
1
receipt_id
receipt_324021030c9d9dbeebf89c009ba88b76306395073189f84e

On-chain effect CallCounter 0 → 1

Recorded Base Sepolia run

Stopped safely before submission

Safe stop
Scheduled for
Network
Base Sepolia
Transaction
None submitted

No transaction was submitted

No on-chain state changed

outcome
PRECONDITION_FAILED
failure_class
submission_rejected
chain_id
84532
externalization_count
0
transaction_hash
null
on_chain_mutation
0

System explanation 03 / From access to evidence

From recurring job to known outcome.

People can use Runrail through the App or API. A recurring job becomes a scheduled run, and Runrail follows that run through limited attempts until it can record an outcome and the evidence that belongs to it.

How a scheduled run moves through Runrail

Access

Wallet sign-in Identity wallet

authentication

Interface App
Programmatic access API credential

authorizes requests

Interface API

Two access paths · One product

Runrail workspace One shared workspace

Jobs, scheduled runs, attempts and results stay separate.

Recurring job Job

Schedule and status

Transaction signing Execution wallet

Submits the scheduled transaction when needed.

Scheduled run Scheduled run

One scheduled time from the recurring job

Execution attempt Attempt(s)

Up to three for this scheduled run

Final outcome

Stop attempting

Can retry

Runrail may try again

Up to 3 attempts per run

Runrail may try again · up to 3 attempts per run

Possible outcomes

01 Confirmed
02 Reverted
03 Other final stops

Exhausted · Blocked · Precondition failed

Confirmation is one outcome. Failures stay visible too.

Execution evidence Receipt · transaction · attempt history · explorer

Successful and failed runs leave a visible record.

First-release scope 04 / Deliberate limits

Clear limits for the first release.

The Public Beta is live on a test network. Transaction value is fixed at zero, each scheduled run has a firm attempt limit, and mainnet use and production service commitments remain outside this release.

Public Beta
Live
Network
Base Sepolia / testnet
Transaction value
0
Attempts per run
Maximum 3
Mainnet
Not enabled
Production SLA
Not offered

Built as a product 05 / Beyond the transaction

The transaction is only one part of the product.

Plutonus built the execution logic together with the App, API, run history and clear release limits. People can schedule work, follow each run and inspect the result.

  • 01 One product through App and API
  • 02 Scheduled work with firm limits
  • 03 Failures that remain visible
  • 04 Outcomes backed by evidence