NO CUSTODY
Ez seed edo private-key custody.
DEVELOPER DOKUMENTAZIOA
Integratu review boundary-a, ez custody boundary-a.
Dokumentazioa transaction security-ra fokuratzen da: SafeSign sarrera, Security Core analisia, authorization eta integration status erreala.
SECURITY MODEL
Lau invariant details baino lehen.
Muga hauek framework-a baino garrantzitsuagoak dira.
PAYLOAD INTEGRITY
Ez aldatu wallet/dApp payload-a.
EXPLICIT AUTHORIZATION
Ez auto-sign edo auto-broadcast; authorization explicitua.
FAIL VISIBLE
Evidence falta = uncertainty, ez silent allow.
REQUEST LIFECYCLE
Request → decode → context → review.
Original request mantendu eta evidence ulergarria gehitu.
REQUEST
Supported request eta context jaso.
DECODE
Method, params, typed data, approvals edo PSBT normalizatu.
CONTEXT
Policy, destination eta simulation evidence gehitu.
REVIEW
Risk/uncertainty SafeSign-en erakutsi; user-ak authorization mantendu.
GUARD / MANIFEST V3
Uneko browser integration foundation.
Chrome/Brave source scaffold-a dago; ethereum.request wrap egiten du eta continue/reject itxaroten du. Production build pipeline falta da.
ethereum.request → SafeSign → original provider
// browser/page context — conceptual integration boundary
const original = ethereum.request.bind(ethereum)
ethereum.request = async (request) => {
const decision = await reviewWithSafeSign(request)
if (decision !== "continue") throw new Error("User rejected")
return original(request) // forward unchanged
}Sensitive ez diren local preferences soilik; inoiz ez keys, seeds, raw signatures edo history osoa.
INTEGRATION STATUS
UI on batek ez du backend capability frogatzen.
Surface bakoitzak bere implementation boundary dauka.
UTXO GUARD
Guard — Manifest V3 foundation dago; production build/distribution aparte.
UTXO WALLET
Wallet — UI dago; real flows SafeSign-etik pasa behar dira.
UTXO RELAY
Relay — route/fee/PSBT analysis dago; signing/execution future integration da.