Skip to content

OFFLINE FIRST · LOCAL WHEN POSSIBLE

Your documents remain accessible.

Gankpo prioritises local execution for suitable operations, then uses the network when transport, issuance or the trust model requires it.

LOCAL.gkpNETWORK WHEN NEEDED

01

Offline First does not mean “never connected”.

CLOUD FIRST

The remote service is the main point of passage.

Core operation first depends on remote infrastructure availability.

GANKPO · OFFLINE FIRST

Local execution is preferred when the model allows it.

The network completes the journey for transport, synchronisation or required external evidence.

02

What can you do without the Internet?

Store a .gkp fileLocal

No network is required merely to store the file on chosen media.

Read structure and metadataLocal

When the application supports the relevant format version.

Check integrity and the primary signatureLocal

From the available bytes, fingerprint and public key.

Open a protected payloadLocal, conditional

Requires the right secret or access key; support varies by application.

Assess a trust chainHybrid

Local when useful anchors and evidence are available; otherwise an update may be required.

Establish a fresh revocation statusHybrid

Cached or embedded evidence may be checked locally; freshness may require synchronisation.

Obtain a trusted timestampConnected

An existing token may be validated locally; obtaining it relies on a TSA.

Prepare or read a .gksend envelopeLocal

Transport through a relay, messaging or another channel remains separate.

Issue or present a remote credentialGenerally connected

Issuer, Connect, OID4VCI and OID4VP exchanges depend on the journey and remote service.

This matrix describes architectural behaviour and its conditions. Exact availability depends on the application, platform, format and qualified version.

LOCAL-FIRST · SEPARATE TRANSPORT

The relay transports. It does not become the authority of truth.

SUITE→RELAIS HTTPS
transport mailbox
→WALLET.gksend
file fallback

03

Autonomy without absolute claims.

01

Autonomy

Continue locally when connectivity is missing.

02

Privacy

Limit systematic transmission.

03

Resilience

Reduce the impact of central outages.

04

Control

Choose storage media.

05

Portability

Move the file through available mechanisms.

06

Continuity

Separate local access from trust services.