⚠️ This project is under active development as part of the Solana Seeker Monolith Hackathon (Q1 2026).

With AlpenSign the Seeker phone can be used to seal bank payments on a public ledger.

AlpenSign turns the Solana Seeker phone — a Web3-native smartphone with hardware-secured key storage — into a Mobile HSM — an independent, client-side device that seals bank payments and Visa/Mastercard 3D-Secure transactions with biometric confirmation and posts the proof to an immutable public ledger.

No bank server. No Apple. No Google. No AlpenSign backend.

The Seeker phone signs, TEEPINTEEPIN (Trusted Execution Environment Platform Infrastructure Network) is a foundational technology architecture developed for the Solana Seeker. It decentralizes mobile device verification by replacing central authorities (Apple/Google) with cryptographic verification backed by economic stakes. Independent Guardians stake SKR tokens to attest that each device's secure element is genuine and untampered. attests, Solana records. The proof lives on a public ledger, not only on the bank's server.

Built on: Seed Vault · TEEPIN/SKR Guardians · Seeker ID · Solana Attestation Service · Solana Mobile Stack / MWA · Soulbound NFTs · WebAuthn

▶ AlpenSign App

📲 dApp Store — coming soon ▶ Promo Video — coming soon Join the Team

Security Comparison

Relative Security Levels in Mobile Banking

Each layer adds independence from centralized trust and strength of evidence in dispute.

App + SMS

App + AccessApp

App + TitanChip + AccessApp

App + Seeker/TEEPIN + AlpenSign

Scale: relative independence from centralized trust & evidence strength in payment disputes. Indicative, not certified.

The Problem

Banks lose billions to fraud — and their only evidence is their own logs.

When a client disputes a payment, the bank's defense rests on server logs they generated, stored, and control. That's self-serving evidence. Courts know it. Regulators know it. Fraudsters know it.

Self-serving evidence — Bank logs prove what the bank says happened. In a dispute, the bank is both record keeper and interested party.
Friendly fraud — Clients dispute legitimate payments. Banks absorb billions because they can't prove the client was present.
Weak authentication proof — SMS OTP, push notifications, app-based 2FA — all bank-controlled or dependent on Apple/Google. No independent trail.
Burden of proof stuck with the bank — Banks must prove authorization with only self-serving logs. AlpenSign enables a potential reversal — the client must explain away an immutable, biometric-confirmed seal.

The Solution

Three layers of trust. Zero trust in intermediaries.

AlpenSign creates an independent evidence chain — from verified hardware through verified identity to immutable proof of authorization.

Genesis Token — Device is genuine

The Seeker's soulbound NFT proves the phone is real hardware, verified by SKR-staked Guardians through TEEPIN. No Apple. No Google. No centralized attestation.

Soulbound NFT · Non-transferable

Bank Credential — Client is verified

The bank issues a credential via Solana Attestation Service to the Seeker wallet, binding the client relationship to the verified device. Revocable by the bank.

SAS Attestation · Revocable

Transaction Seal — Payment is authorized

Client reviews payment details on-device, confirms with biometric. The Seeker's secure element signs and the proof is posted to Solana. Permanent. Immutable.

Biometric + Secure Element

✓

Dispute? Rejected.

Bank checks: Genesis Token (real device) + credential (our client) + seal (biometric confirmed). Independent evidence chain. The burden of proof shifts — the client must explain away a cryptographic seal they created.

Transaction Sealing Flow

Setup & Enrollment Flow

TEEPIN & SKR Economy

Why you can trust the device — without trusting AlpenSign.

Traditional device attestation depends on Apple or Google saying “this phone is genuine.” TEEPIN replaces that with economic skin-in-the-game: independent Guardians stake SKR tokens to attest Seeker hardware integrity. If a Guardian falsely attests a compromised device, they lose their stake. For banks, this means the device behind every AlpenSign seal is verified by a decentralized network with real financial consequences — not by a vendor’s promise.

⚖️

Guardians, not Gatekeepers

SKR-staked Guardians independently verify that each Seeker’s Trusted Execution Environment is untampered. No single entity controls attestation, and no single entity can revoke it.

🩺

Economic Guarantee

Device integrity isn’t just a technical claim — it’s backed by staked capital. Fraudulent attestation means slashing. This gives banks a trust anchor that doesn’t depend on AlpenSign, Apple, or Google remaining cooperative.

The Team

Meet Our Monolith Hackathon Team

Roman

Founder · Product Mgmt, Dev

redpill.skr

Alexandr

Fullstack Dev (Demo Backend)

Building the demo backend and Solana integration layer.

⌘

AI: Claude + Gemini

AI Engineering Partner

Anthropic Claude and Google Gemini

Why Solana Seeker?

What's not possible on iPhone or Pixel.

No on-chain device identity — Apple and Google have no equivalent to the Genesis Token. You cannot prove on a public ledger which specific device signed.
No decentralized device attestation — Play Integrity and DeviceCheck are centralized, opaque, and revocable by the vendor at any time.
No native Solana signing in the secure element — Seed Vault signs Solana transactions directly inside the hardware. On iOS/Android, there is no OS-level blockchain signing integration.
No vendor-free trust chain — On iPhone, Apple sits in the middle. On Pixel, Google does. Either can change terms, revoke attestation, or shut down APIs unilaterally. Banks have zero recourse.
No direct-to-chain posting from the device — Solana Mobile Stack lets the dApp submit transactions without a server relay. On iOS/Android, you'd need a backend intermediary — adding a trust dependency.

Regulatory Compliance & Alignment

Designed with regulation in mind.

AlpenSign's architecture aligns with existing and emerging regulatory frameworks for electronic signatures, data protection, and financial services compliance.

QES-comparable — Biometric + secure element + hardware-isolated keys: structurally equivalent to Qualified Electronic Signatures under eIDAS
GDPR by design — No personal data on-chain. Only cryptographic hashes. Biometrics stay on-device.
Immutable audit trail — Timestamped, tamper-proof record on Solana. Supports FINMA, MiFID II, and PSD2/SCA requirements.
Swiss & EU compatible — Aligns with ZertES, eIDAS trust services, and PSD2 independent authentication requirements.

Built With

Solana-native. Seeker-optimized. Bank-ready.

🔐

Seeker Seed Vault

Hardware-isolated key storage with biometric-gated signing. Keys never leave the secure element. The Genesis Token anchors device identity on-chain.

📜

Solana Attestation Service

On-chain attestation protocol for issuing verifiable credentials and transaction seals. AlpenSign uses SAS for both bank credential binding and payment seal records. No custom smart contracts needed.

⚡

Solana Mobile Stack

Native wallet integration via Mobile Wallet Adapter (MWA), dApp runtime, and TEEPIN device verification. The Seeker is the only phone where secure signing and Solana attestation are integrated at the OS level.

🛡️

TEEPIN + SKR Guardians

Trusted Execution Environment Platform Infrastructure Network. SKR-staked Guardians verify device authenticity — the economic security layer behind the Genesis Token.

Open to Contributors

Help us seal the deal.

We're looking for Solana developers, security engineers, and anyone who believes banking shouldn't depend on one company's goodwill.

View on GitHub Contact Team

✓ Copied — paste into Claude or any LLM