Expiry awareness
The wallet can compute expiry height, blocks to expiry, status, and dust-risk style warnings so lifecycle risk is visible before it becomes a crisis.
Wallet layer
A lifecycle wallet stack built for explicit renewal workflows.
OBTC's long-term sustainability thesis depends on active ownership that users can actually manage. The current wallet direction includes expiry awareness, manual renewal, batch renewal, and controlled automation surfaces, with funded renewal claims kept evidence-gated until public txids are linked.
Current surfaces
obtc.getexpiry, obtc.renew, and renewall
Automation path Auto-Renew remains default-off; controlled wallet orchestration is the review target
Boundary wallet and product layer, not consensus
Current wallet direction
The wallet story is already concrete: inspect, preview, renew, and audit.
Manual renewal
obtc.getexpiry exposes the risk view, while obtc.renew lets holders renew selected outputs directly.
Batch maintenance
renewall turns renewal into a repeatable workflow instead of a one-output-at-a-time ritual.
Process-local Auto-Renew
The current scheduler runs inside the wallet process with windows, fee limits, and failure backoff. It is an execution aid, not a hidden chain rule.
Controlled automation
Automation works best when planning, signing, and policy stay legible.
Inspect
Start with expiry risk, not blind execution. The wallet can surface which outputs are safe, expiring, or already expired.
Preview
The automation path is meant to stage renewal work before publication, not jump straight to opaque action.
Separate roles
The wallet automation surface handles capability, policy, signer-session, and renewal orchestration. An optional Remote Signer can sit behind it when signing needs stronger isolation.
Record
Automated stewardship only helps if operators can review what happened. Operation metadata and audit trails are part of the point.
What the automation surface is
An orchestration surface for expiry analysis, preview, authorization, and renewal execution in the wallet layer.
What the automation surface is not
It is not the remote signer itself. Remote signing remains an optional separate backend for deployments that want a stronger split between planning and signing.
Testnet v0.1
OBTCWallet has a source-only engineering preview for the core wallet paths.The preview documents native OBTC network flags, the 19528 node RPC default, the 19554 wallet legacy RPC default, obtc.getexpiry, obtc.renew, and renewall --dry-run. Funded renewal and non-dry-run batch renewal claims remain evidence-gated until public txids, commands, commit hashes, and heights are linked. It is not a production wallet release.
External support boundary
Limited reviewer onboarding is invite-only, and wallet support stays inside documented testnet paths.There is no public faucet. Testnet coins are manually issued for invited reviewers. Auto-Renew remains default-off, and Remote Signer is outside v0.1 external support.
Boundary
The wallet-layer case for OBTC is practical: lifecycle risk can be observed, renewed, budgeted, and audited without moving those rules into consensus.