UTXOSUITE — home
GARATZAILE-PLATAFORMA

Txertatu transakzio-segurtasuna sinadura-fluxuan.

SafeSign wallet, fintech eta onchain aplikazioetarako integrazio-geruza gisa eraikitzen ari da: eskaera deskodetu, segurtasun-testuingurua gehitu, payload-a mantendu eta baimen esplizitua eskatu.

Arkitektura ikusi ↗Integrazioaz hitz egin →
SAFESIGN / PRE-PRODUCTIONNON-CUSTODIALEXPLICIT AUTHORIZATION14 LOCALES
DEVELOPERS / INTEGRATION SURFACEGarapen-postu bat gela ilun batean, bi pantaila kodearekin irekita.
INTEGRAZIO-AZALERAK

Motor bat, integratzeko hainbat modu.

Produktu-kontratua UTXO ekosistema zaharra baino estuagoa da. Integrazioek SafeSign-en erabakiak eta ebidentzia erakutsi behar dituzte, ez business edo office produktuak nahasi.

01CONTRACT STABILIZATION

SafeSign Decision SDK

Supported request-ak deskodetu, intentua adierazi, ebidentzia erantsi eta ALLOW / WARN / REVIEW / BLOCK gomendioak emateko kontratua.

context + payload → evidence + decision
02SOURCE PRIMITIVES

Security Core

SafeSign, Guard eta wallet integrazioetan berrerabiltzeko local-first analisi eta policy primitibak, key custody edo signing authority gabe.

deterministic rules → explainable signals
03MV3 SOURCE SCAFFOLD

UTXO Guard

Browser surface-a supported request-ak wrap eta SafeSign review erakusteko, originala aldatu gabe bidali aurretik.

provider request → explicit continue / reject
04PLANNED

Enterprise Policy

Signed organization policy, approvals eta deployment controls analysis core-aren gainean joan behar dira, decision contract eta audit boundary egonkortu ondoren.

signed policy → organization decision constraints
EBIDENTZIA-MUGA

Esan zehazki zer dagoen.

Enterprise erosleek claims egiaztatuko dituzte. Horregatik, oraingo source artefaktuak eta oraindik balidazioa edo review independentea behar duten production gaitasunak bereizten dira.

CURRENT

Uneko repository-ebidentzia

  • SafeSign product surface fokalizatua eta transaction-security arkitektura.
  • Security Core source kontzeptuak decoding, rules, validation eta policy boundary-entzat.
  • Guard Manifest V3 scaffold eta continue/reject interaction model esplizitua.
NOT YET

Oraindik ez da production claim bat

  • Ez da production SLA edo independent verified audit claim-ik egiten.
  • Ez da universal chain coverage, real-time threat network edo sub-second guarantee saldu behar neurketa egin arte.
  • Production API packaging, auth, quotas, billing eta support contracts oraindik osatu behar dira.
BIDE KOMERTZIALAK

Segurtasun-core bera sakonera desberdinetan monetizatu.

Ereduak self-service integrazioetatik enterprise kontratuetara eskalatu behar du, segmentu bakoitzerako produktu desberdinak sortu gabe.

01

Developer

Self-service evaluation, reference contracts, local analysis eta docs; adoption procurement friction aurretik.

EVALUATION / ADOPTION
02

Product

Usage-based edo contracted integration wallet, fintech eta onchain products-entzat, API guarantees neurgarriak direnean.

SDK / API REVENUE
03

Enterprise

Policy enforcement, private deployment, procurement evidence, support commitments eta multi-approval dira institutional layer-a.

ANNUAL CONTRACT / PRIVATE DEPLOYMENT
HELBURU-KONTRATUA

Erabaki-interfaze egonkorra, ez beste wallet bat.

SDK/API-ak contextua eta aldatu gabeko signing payload-a hartu eta ebidentzia egituratua eta gomendioa itzuli behar ditu. Signing authority integratzailearen wallet-ean geratzen da.

SAFESIGN / DECISION CONTRACTILLUSTRATIVE TARGET
// Target interface — illustrative, not a published package
const review = await safeSign.review({
  origin,
  chainId,
  method,
  payload,        // preserved unchanged
  expectedIntent, // optional user/app intent
});

review.decision // ALLOW | WARN | REVIEW | BLOCK
review.evidence // structured, explainable signals
review.payload  // same signing payload supplied by integrator
SafeSign →Security Core →UTXO Guard →Integrazioaz hitz egin →
DEVELOPERS / INTEGRATION CONTRACT

Review integratu signing boundary galdu gabe.

Integration contract side-effect free: request in, evidence out, payload preserved, signer authoritative.

INTEGRATION SURFACES

Signing request dagoen lekuan hasi.

Review narrow reliable boundary-an gehitu wallet transport/custody/signing berreraiki gabe.

01

WALLET EXTENSION

Provider methods confirmation aurretik interceptatu eta evidence erakutsi original request ordezkatu gabe.

02

EMBEDDED WALLET

Request build ondoren eta signer invocation aurretik analizatu; keys analysis-tik kanpo.

03

FINTECH APPROVAL FLOW

Evidence + policy institution signer/custody-ra bidali aurretik exekutatu.

04

AGENT / AUTOMATION

Machine-generated intent untrusted input da; irreversible/high-value actions-rako policy gates + human escalation.

05

TRANSACTION BUILDER

Final payload analizatu, ez pre-construction params bakarrik, encoding/routing-ek review saihestu ez dezaten.

06

READ-ONLY MONITORING

Evidence model post-event observability eta incident triage-rako berrerabili signing authority eman gabe.

Evidence model

Eraiki decision bat independent signals erabiliz.

Unknown evidence ezezagun bezala ikusgai mantendu behar da; missing analysis ez da inoiz ALLOW bihurtu behar.

01CAPTURE

Request zehatza eta origin confirmation aurretik jaso.

02CLASSIFY

Request family identifikatu generic risk logic aurretik.

03DECODE

Methods, parameters, authority eta destinations normalizatu.

04ENRICH

Contract, policy, freshness eta simulation context gehitu eskuragarri dagoenean.

05COMPARE

Reconstructed authority user intent-arekin alderatu.

06DECIDE

ALLOW/WARN/REVIEW/BLOCK reasons eta unknowns-ekin itzuli.

07AUTHORIZE

Control wallet/signer-era itzuli; analysis-ek ez du silent sign/broadcast egiten.

Decision contract

Decision contract

Integration contract side-effect free: request in, evidence out, payload preserved, signer authoritative.

REQUEST / INPUT
{
  "requestType": "eip712",
  "origin": "https://app.example",
  "chainId": 1,
  "method": "eth_signTypedData_v4",
  "intent": { "action": "swap", "asset": "USDC" },
  "payload": "<original wallet payload>"
}
DECISION / OUTPUT
{
  "decision": "REVIEW",
  "confidence": "partial",
  "authority": [{ "type": "token_spend", "scope": "unlimited" }],
  "evidence": [{ "signal": "new_spender", "severity": "high" }],
  "unknowns": ["future_execution_state"],
  "payloadIntegrity": "unchanged"
}
Decision semantics

Decision semantics

Unknown evidence ezezagun bezala ikusgai mantendu behar da; missing analysis ez da inoiz ALLOW bihurtu behar.

DECISION
TRIGGER
MEANING
NEXT
ALLOW
supported evidence consistent
Supported evidence-n contradiction materialik ez; explicit authorization behar da.
EXPLICIT SIGN
WARN
material risk present
Request ulertzen da, baina material risk authorization aurretik erakutsi behar da.
USER REVIEW
REVIEW
incomplete or conflicting evidence
Evidence incomplete, contradictory edo policy-tik kanpo; escalate egin.
SECOND REVIEW
BLOCK
policy or supported threat signal
Policy/threat signal-ek request gelditu behar dela dio explicit override gabe.
NO FORWARD
POLICY / FAILURE MODES

Analysis degradatzen denean fail-safe egin.

Unknown evidence ezezagun bezala ikusgai mantendu behar da; missing analysis ez da inoiz ALLOW bihurtu behar.

UNSUPPORTED REQUEST

Ez asmatu. Request preserve, unsupported surface erakutsi eta review eskatu.

unsupported → REVIEW

SIMULATION UNAVAILABLE

Static/context evidence erabili, baina missing simulation esplizitu egin.

simulation: unavailable → confidence: partial

INTENT MISMATCH

Intent eta decoded authority mismatch first-class evidence da.

intent != authority → REVIEW/BLOCK policy

STALE CONTEXT

Time-sensitive intelligence-k freshness metadata behar du old evidence current fact bezala ez agertzeko.

observedAt + ttl → freshness
INVARIANT

Integration failure visible, payload integrity, unsupported states eta no implicit approval.

EIP-712 ↗ERC-2612 ↗BIP-174 ↗OWASP SCSVS ↗