Part III permits directive steps including freezing specified UTXOs and reassigning frozen coins.
Can BSV freeze or reassign coins?
“An authority can freeze UTXOs and transfer coins without the owner's signature. That destroys bearer ownership.”
Real tradeoff · Updated 2026-10-05 · Next review 2026-11-05
By BSV.place / Project Babbage. Editorial review; source access dates below. No independent product retest is implied.
The short answer
Yes, the Network Access Rules list directives that may freeze specified UTXOs, reassign frozen coins, alter peer access, or invalidate specified blocks after defined events. A reassignment enforced by nodes is not the same mechanism as forging the owner's signature or learning a private key, but it can change which spend the network accepts. That weakens pure bearer finality and creates legal-process and governance dependencies.
Identify the authority at each step
The stated recovery rationale concerns disputed or recoverable property. Whether a particular use is justified depends on its evidence, authority and process; the design rationale is not proof of correct use. Part III contains different event categories, so do not assume every directive has the same court-order prerequisite.
A network-enforced change to accepted spending is consequential even when it does not extract a user’s key or forge an application signature. Keep the accepted-coin effect separate from the cryptographic authority needed for unrelated app operations.
| Stage | Question |
|---|---|
| Event or external input | What evidence and applicable provision trigger the process? |
| Association decision | Who is empowered, under what scope and restrictions? |
| Signed communication | Which instruction is attributed to which authority? |
| Node treatment | What coin or block effect is enforced? |
| Challenge and outcome | What review route and unresolved disagreement remain? |
The objection's strongest ground
- Part III expressly lists freezing UTXOs and reassigning frozen coins among permitted directive steps.
- Node enforcement can change accepted ledger state without producing the former holder's signature.
- Users who require a ledger incapable of legal recovery intervention may reasonably reject this model.
Do not claim more than the evidence
- Published restrictions do not guarantee correct courts, narrow use, transparent execution, or effective recourse.
- The mechanism does not, by itself, disclose private keys, decrypt data, or let an application impersonate a user.
- This site offers no legal conclusion about title, enforceability, or jurisdiction.
What to inspect next
- Read every Part III trigger, restriction, and permitted step—not just summaries branded for or against DAR.
- Trace the applicable event and authority through Association decision, signed message, node action and resulting coin or block treatment. The event categories differ.
- Ask for a complete directive register, case documents, key-holder controls, notice, appeal, and post-incident review.
What would change this answer?
Secret directives, broad triggers, unavailable challenge, or implementation beyond published authority would worsen the assessment. Narrow, independently audited, transparent process with effective correction would improve it.
What the cited sources establish
Directive messages are delivered through a signed node alert mechanism.