Question 1

What is Seeker (SKR)?

Accepted Answer

Seeker is a decentralised mobile platform that reimagines mobile infrastructure through verifiable identity, decentralised governance, and secure app curation. It introduces an open mobile stack designed to eliminate centralised gatekeeping, leveraging cryptographic proofs and community governance to enable a secure and permissionless ecosystem.

At the core of Seeker is a hardware-software architecture built on mobile devices that include a Trusted Execution Environment (TEE). These TEEs generate cryptographic attestations of device state and software integrity. Attestations are submitted to a decentralised validator network for verification and serve as the foundation for secure identity, access control, and decentralised coordination across the platform.

Seeker integrates these elements through a protocol called TEEPIN (Trusted Execution Environment Platform Infrastructure Network), which coordinates validation of devices, reviews of applications, and governance of the protocol. This infrastructure replaces the conventional mobile app store model with a trust-minimised, on-chain governance and review process that can be audited and participated in by any user.

The operating system in Seeker devices supports runtime controls, secure installation, and decentralised enforcement of access and usage policies. Developers interact with the system through APIs that allow them to query device integrity, enforce compliance rules, and submit applications for decentralised review.

Question 2

What is Seeker (SKR) used for?

Accepted Answer

SKR is the protocol’s native token and coordination asset. It enables validation, review, governance, and enforcement mechanisms within the Seeker ecosystem. It is used for:

- **Device attestation validation** - Participants use SKR to operate validation nodes that assess hardware-generated attestations submitted by devices for authenticity and compliance.
- **Application review and publishing** - Developers must interact with the protocol using SKR to submit applications for decentralised review. The token is used to ensure accountability and enable penalties for violations.
- **Delegated protocol governance** - Token holders can assign voting weight to validator participants who make decisions regarding ecosystem rules, content policy, and network updates.
- **Role-based access and coordination** - SKR may be integrated into role-specific permissions, including who can approve devices, curate applications, or participate in protocol functions.
- **Protocol alignment** - SKR serves as the basis for incentive structures that ensure the correctness and resilience of protocol operations across a wide range of participants.

SKR is not used for speculative financial purposes in the design of the protocol. Its role is limited to enabling cryptographic security, governance participation, and review accountability within the Seeker ecosystem.

Question 3

How does the Seeker protocol work?

Accepted Answer

The Seeker architecture operates across three core layers:

- **Hardware Layer** - Devices include a Trusted Execution Environment (TEE) that produces signed attestations of boot state, OS integrity, and runtime behaviour. This allows verifiable device identity and prevents software tampering.
- **Protocol Layer** - The TEEPIN network receives and verifies device attestations, curates submitted applications, enforces policy decisions, and coordinates actions among network validators. It maintains a public state of device validity, application status, and governance decisions.
- **Governance Layer** - Elected validators, known as Guardians, review application submissions, verify devices, and participate in the creation and enforcement of content policies. Delegated participation allows token holders to assign representation without direct involvement.

Together, these layers support a decentralised mobile system where device-level trust is established cryptographically and decision-making is handled transparently through protocol-defined rules and on-chain consensus.

Question 4

What is TEEPIN?

Accepted Answer

TEEPIN is the infrastructure layer that coordinates all core functions in Seeker. It includes:

- **Device verification** - Cryptographic proofs from device TEEs are evaluated for authenticity, compliance, and security state. Only verified devices can participate in the ecosystem.
- **Application governance** - New apps are reviewed by network validators. Static and dynamic analysis is performed to assess functionality, compliance with policy, and safety. Results are stored in a shared protocol state.
- **Policy enforcement** - Protocol rules regarding device onboarding, app publication, and security practices are enforced automatically by smart contracts and verified actors.
- **Validator coordination** - The system manages the actions and responsibilities of Guardians, including verification, voting, and dispute resolution.

TEEPIN abstracts the role of traditional centralised administrators and replaces them with protocol-enforced, cryptographically backed logic and transparent governance participation.

Question 5

How does Seeker handle decentralised app curation?

Accepted Answer

The application layer in Seeker supports decentralised curation through two roles:

- **Guardians** - Elected validators who perform the formal review and acceptance process for app submissions. Their responsibilities include security checks, content policy validation, and ensuring functional integrity. Approved apps are made available via the decentralised Seeker store.
- **Curators** - Broader ecosystem participants who flag and rate applications over time. They provide signals related to app performance, reliability, and behaviour, which influence app rankings and visibility within the ecosystem.

This model allows Seeker to support a dynamic and high-integrity application ecosystem without relying on a single entity to make or enforce decisions.

Question 6

How does hardware identity work in Seeker?

Accepted Answer

Hardware-based identity is central to Seeker’s trust model. Every participating device includes a TEE that performs the following:

- **Generates cryptographic keys** tied to the physical device
- **Signs measurements of device software** and boot state
- **Provides attestations** that are verifiable by the network

These attestations enable:

- **Sybil resistance** - Preventing multiple identities per physical device
- **Secure gating** - Applications can restrict access to trusted devices
- **On-chain enforceability** - Smart contracts can verify the origin and integrity of the device interacting with them

This model ensures that ecosystem security originates from hardware-level guarantees, not external verification or user claims.