Scope
SafeSign, Security Core, Academy eta Guard/Wallet/Relay integration work. Research eta experiments ez dira automatikoki commercial releases.
Current product model eta privacy/security boundaries azaltzen ditu; ez da offer-specific contract bat.
SafeSign, Security Core, Academy eta Guard/Wallet/Relay integration work. Research eta experiments ez dira automatikoki commercial releases.
Data-minimizing eta local-first ahal denean; ez seed/private-key custody. Future hosted services-ek controller/purpose/retention argitaratu behar dute.
Analysis-ek uncertainty murrizten du, ez risk ezabatzen. Missing evidence uncertainty da.
Ez server-side seed/key custody, auto-sign edo auto-broadcast default gisa; user/wallet authorization boundary.
UI, scaffold, prototype eta production states desberdinak dira; commit ≠ release/audit.
Paid offer aurretik seller, price, taxes, cancellation/refund eta actual terms argitaratu behar dira; hemen ez dira asmatzen.
Actual controller/jurisdiction-ek definitzen dituzte rights; verified contact behar da data collection aurretik.
Revised: 26 August 2026 · development track
Legal surface-ak technical boundary islatu behar du: zer analyze, zer ez controlatu eta zer uncertainty geratzen den.
Request-ak zer authorize dezakeen deskribatu: transfer, allowance, operator rights, typed data edo Bitcoin outputs.
method · spender · scope · outputsUnknown implementation, stale context edo unavailable simulation ikusgai geratzen dira eta REVIEW igo dezakete.
unknowns · freshness · contradictionsAnalysis-ek ez du seed/private key behar eta ez da signing authority bihurtu behar.
no seed · no key custody · no auto-signReleased, audited, peer-reviewed eta production-ready evidence claims dira.
artifact · test · review · operations