Resource · 2.8 in the design proposal

Utility (testnet-only)

The smallest resource in the proposal — one operation, purely for development against Accumulate's public testnet — and an open question about whether it should ship at all.

1 operation Phase 2+ · testnet-only

Why a faucet operation exists in a workflow node at all

Per 004.References/AboutAcmeNetSdk.md, the SDK's quick-start example connects to https://kermit.accumulatenetwork.io — Accumulate's public testnet (Kermit), which also has its own public explorer for verifying transactions during development. A Lite Account — the unstructured, address-like account type covered in 004.References/AboutAccumulate.md §2 — is free to create but isn't acknowledged by the network until it holds ACME. On testnet, that ACME comes from a faucet rather than a real purchase, which is what UT01 wraps.

Operations

Code	Operation	Maps to	Why a workflow author wants it	Priority
UT01	Request Faucet Funds	V2 `faucet` / `TxBody.AcmeFaucet()`	Fund a test Lite Account with test-ACME during development	Phase 2

How it works — bootstrapping a dev/test signer

UT01 — the only pre-funding path that doesn't require existing ACME

sequenceDiagram
  participant Dev as Developer / dev workflow
  participant SS01 as SS01 Generate Signing Keypair
  participant UT01 as UT01 Request Faucet Funds
  participant Kermit as Kermit testnet
  participant CR01 as CR01 Add Credits

  Dev->>SS01: generate Ed25519 keypair
  SS01-->>Dev: keypair (Lite Identity derives from it)
  Dev->>UT01: request faucet funds for the Lite Account
  UT01->>Kermit: V2 faucet / TxBody.AcmeFaucet()
  Kermit-->>UT01: test-ACME credited
  Dev->>CR01: Add Credits (convert test-ACME -> credits)
  CR01-->>Dev: signer now funded enough to write on testnet

No business use case in scope

Unlike every other resource on this site, 001.BusinessIdeas/README.md has no dedicated use-case entry for Utility — it's development/testing plumbing, not a workflow capability a business user would reach for. Rather than invent a callout that doesn't exist in the source material, this page states that gap plainly.

Open questions affecting this resource

Open · Faucet in a production tool

Should a testnet-only faucet operation ship in the node at all, or be excluded/gated so it can't accidentally appear as an option in a production workflow? This is the entire open-question surface for this resource — a one-operation resource with a one-line but consequential design question attached to it.