Android-first mobile threat defense

Security signals.Accountable decisions.

Valkirie Shield turns Android threat signals into a server-side risk decision. The full assessment stays private; a compact cryptographic commitment can be anchored to Solana Devnet so later changes are detectable.

Explore the approach

Hackathon prototype · Real rules and audit code · Simulated attestation in the demo

01 / The approach

How it works

The phone supplies evidence. The backend makes the decision. The audit record makes later changes detectable without publishing a private report.

01 / COLLECT

Read local signals

Android reports the security checks available on the device. These are client-reported signals, not verified facts.

02 / ASSESS

Calculate risk

Versioned, deterministic rules turn the submitted evidence into a risk score and triggered findings on the server.

03 / PRESERVE

Store the report

PostgreSQL retains the complete assessment and canonical evidence needed to reproduce its hash.

04 / ANCHOR

Track the proof

When configured, a worker submits compact hash evidence to Solana Devnet and tracks confirmation separately from the verdict.

02 / Protection model

A stronger decision starts with a clear trust boundary.

The Android app reports local checks, but it does not get to assign its own security verdict. Versioned rules on the backend calculate risk and record which findings led to the result.

  • Server-owned verdictRoot, debugger, emulator, hooking and tampering signals feed a deterministic assessment; client reports remain evidence, not independent proof.
  • Private by designComplete assessments remain in PostgreSQL. Raw tokens, identities and device details are not placed on-chain.
  • Verification is a separate layerPasskeys and genuine Google Play Integrity checks are planned. The current staging demo labels simulated authentication and attestation as mock.
03 / Solana audit

A receipt on-chain. The report off-chain.

Why blockchain here? It offers an external place to compare an assessment’s cryptographic fingerprint later. Valkirie Shield stores the complete report privately, hashes its canonical representation with SHA-256, and prepares a compact Solana Devnet Memo commitment when the audit worker is configured.

The assessment returns independently of the chain. A submitted transaction is only an attempt; the audit state becomes confirmed after the worker verifies a successful finalized transaction with the expected Memo and signer.

What the chain recordsSolana Devnet
01
Canonical report hash

A versioned SHA-256 digest represents the stored assessment.

02
Signed Memo transaction

The backend signer submits the compact commitment; Android does not hold an audit key.

03
Finalized audit status

The transaction reference is exposed only after confirmation checks succeed.

The chain can help detect a changed report. It cannot prove that client signals were true, the risk decision was correct, or a device was safe.

04 / Current build

Prototype status

A working backend path exists today. The demo makes its simulated integrations explicit so a mock result cannot be mistaken for device verification.

Implemented

The assessment core

The backend can register devices, evaluate security signals, persist assessments, and queue audit work in the same database transaction.

  • Deterministic risk rules and recorded findings
  • Canonical SHA-256 assessment commitments
  • Audit worker with submission and confirmation states, enabled by configuration
Staging simulation

Honest demo boundaries

The end-to-end staging flow simulates authentication and Play Integrity. Results are marked mock; they do not establish verified device integrity.

  • Passkey verification is not implemented yet
  • Google Play Integrity token verification is not implemented yet
  • Public Devnet anchoring has not been verified end to end

A hash on-chain can show that a committed assessment has not changed. It does not independently prove that a device was safe.

05 / Road ahead

What’s next

The next milestone is a verified flow on a real Android device, with authentication, attestation, assessment, and independently checkable audit evidence.

  1. 01
    Passkey ownership

    Use Android Credential Manager and backend WebAuthn verification to bind an assessment to the credential holder.

  2. 02
    Verified app integrity

    Validate Google Play Integrity evidence, app identity, request binding, and freshness on the server.

  3. 03
    Real-device proof

    Complete a Play-recognized Android run and independently verify a finalized Solana Devnet commitment.