GOVERNMENT
Public services that verify the action, not just the citizen
Agencies have spent years proving who citizens are. Fraud still gets through, because a verified identity can be borrowed, stolen or impersonated. UniKey lets an agency check that a specific filing, payment or change was authorized by its owner before it is processed.
THE PROBLEM TODAY
Credentials stand in for permission
Benefit redirection
A claimant's payment details are changed by someone who passed the identity check.
Filing fraud
Returns and applications are submitted in a citizen's name with stolen credentials.
Inter-agency trust
Agencies exchange requests and data with no proof the sending official was authorized.
WITH UNIKEY
Actions that carry a Trust Packet
Each one is signed by the party with the authority to take it, and verified before it executes.
-
Change payment details
Benefit payment changes need a packet from the claimant's own device.
-
File an application
Applications and returns carry the filer's authorization, verified against DNS-published keys.
-
Approve a permit
Officials sign approvals within the scope delegated to them, and the delegation chain is recorded.
-
Share between agencies
Requests from another agency carry its authority anchor, checked before any data is released.
{
"action": "update_benefit_payment",
"subject": "claimant-58213@benefits.state.example",
"signer": "benefits.state.example",
"audience": "payments@treasury.state.example",
"params": {
"claim_id": "UI-2026-58213",
"routing_number": "011000015"
},
"expires_at": "2026-10-05T14:05:00Z"
}
Illustrative. The verifier looks up the signer's public key in DNS, checks the Ed25519 signature, refuses a packet it has seen before or one past its expiry, and only then lets the action run.
DEMO VIDEOS
Shape what comes next
A Government app is on the demo roadmap: a state or local agency handling benefits and filings.
MORE INDUSTRIES