Hypergolic

Hypergolic v0.2.0

Capability table

See which capabilities napplets can use in Hypergolic and what remains to implement or test.

Estimated compatibility

85%

124 of 146 sampled napplets match on required capabilities.

Historical sample · 3 relays · 20 Nov 2026, 05:20 UTC

How it’s counted

Each eligible root or named publication counts once. A napplet matches when every required domain in its signed manifest has Full or Partial support in Hypergolic v0.2.0. A napplet with no required domains also matches. Optional domains have no effect on the count.

Partial support may omit an operation a napplet needs. The estimate covers publications observed on the sampled relays. Inspect the publications and relay coverage.

Full support means the release implements the required behavior in the cited draft. An empty badge means release testing is pending. A checked badge links to the end-to-end test and names the devices that passed.

How to read the token estimates

Each T-shirt size estimates total coding-agent input and output tokens for one domain. It covers source review, implementation, tests, Android and iOS acceptance, and one fix cycle. These planning estimates credit reusable Hypergolic code and assume one viable backend. Adding them together would double-count shared work.

XXS
under 15k
XS
15k–40k
S
40k–100k
M
100k–250k
L
250k–500k
XL
500k–900k
XXL
900k–2M+

These estimates date from 19 November 2026. They cover the original scope, including testing.

Filter by support status

Hypergolic v0.2.0 capability support and available operations
Capability domainv0.2.0What a napplet getsRemaining workSize estimate
Agent tokens
storage Full supportAndroid 16 phoneiPhone 16 (iOS 27.0.1)All four storage operations (get, set, remove, keys) in both shared and per-instance storage.None for the tested v0.2.0 cases.Release contractStorage operationsStorage draftNo estimate
common Full supportAndroid 16 phoneiPhone 16 (iOS 27.0.1)All eight operations, including NIP-19 conversion, profile and follow reads, follow changes, reactions and reports. Social writes require approval. Each signed event must fit within 8 KiB.None for the tested v0.2.0 cases.Release social operationsSocial publicationCommon draft
S 40k–100k
config Partial supportSaved per-napplet settings using a supported subset of configuration schemas.Return a closable subscription from onSchemaError. Support valid schemas that exceed the release’s string and array limits, then verify registration and updates on devices.Release behaviorSchema validationConfig draft
S 40k–100k
cvm Partial supportEncrypted requests to known, free providers. Discovery, registry execution, and payments are unavailable.Implement provider discovery and registry lookup, description and execution. Verify direct calls with a real free provider. Paid calls also need budgets, consent and settlement.CVM profileCVM request dispatchCVM draft
Free-provider profileS 40k–100k
Broader paid ecosystemXXL 900k–2M
identity Partial supportPublic profile, relay preferences, follows, mutes and selected lists for the active account.Add blocked-user and zap-history reads. Both currently return an error. The estimate covers read-only history.Release identity coverageIdentity readsIdentity draft
M 100k–250k
inc Partial supportMessages and channels between active napplet sessions.Address each running instance separately. The release uses an app label, so two instances of the same napplet cannot be targeted independently. Verify delivery and closure between instances.Release routingChannel routingINC draft
S 40k–100k
intent Partial supportDispatch to installed handlers. Discovery of uninstalled handlers is unavailable.Resolve root manifests (kind 15129) alongside named manifests and snapshots. Verify discovery, installation consent and delivery to a previously uninstalled handler.Release routingManifest selectionIntent draft
M 100k–250k
keys Partial supportHardware keyboard actions and shortcuts for the focused napplet.Forward eligible unbound key combinations to the shell. The release drops every combination with a modifier. Verify forwarding, bindings and reserved shortcuts with physical keyboards.Release key policyKey forwardingKeys draft
S 40k–100k
link Full supportAndroid 16 phoneiPhone 16 (iOS 27.0.1)Opens an approved HTTPS link with the device’s handler and reports the outcome. The release allows HTTPS only.None for the tested v0.2.0 cases.Release link policyLink request handlingLink draft
XS 15k–40k
media Partial supportForeground HTTPS MP4 playback and bounded MP3 radio.Deliver session metadata updates to the player. The guest can send an update, but the runtime drops it. Verify title changes and playback controls on both native players.Release playback profileMedia message handlingMedia draft
L 250k–500k
notify Full supportAndroid 16 phoneiPhone 16 (iOS 27.0.1)In-app notifications with channel permissions, badges, action buttons, body clicks and dismissals.None for the tested v0.2.0 cases.Release behaviorNotification centreNotify draft
S 40k–100k
outbox Partial supportRelay resolution, event lookup, queries, subscriptions, and approved publication under the release’s routing limits.Limit each publication to the single signed event allowed by the draft. The release can also send a signed relay list. Verify routing with real relays on both platforms.Release routing and divergencePublication planOutbox draft
S 40k–100k
relay Partial supportQueries, subscriptions, and approved publication. Encrypted publication is unavailable.Implement encrypted publication and decrypt incoming encrypted events for the intended recipient. Verify both directions with real relays.Release contractSubscription deliveryRelay draft
L 250k–500k
resource Partial supportBounded HTTPS, Blossom, one-hop Nostr, and data: reads.Return canonical base64 in public byte results. The release returns a Blob. Check the revised format for single reads, bulk results and cancellation.Release resource profileResource responseResource draft
M 100k–250k
shell Partial supportStartup handshake and capability discovery for the calling napplet.Allow an authenticated napplet to use its other granted domains before the shell handshake completes. The release waits for the handshake. Verify early calls on both platforms.ExtensionSession readinessShell draft
XS 15k–40k
theme Full supportAndroid 16 phoneiPhone 16 (iOS 27.0.1)Supplies background, text and primary colours and broadcasts changes when the system switches appearance.None for the tested v0.2.0 cases.Theme serviceTheme draft
XS 15k–40k
upload Full supportAndroid 16 phoneiPhone 16 (iOS 27.0.1)Uploads approved raw bytes to Blossom, reports progress and returns a URL, SHA-256 hash, size and media type.None for the tested v0.2.0 cases.Release upload workflowUpload completionUpload draft
M 100k–250k
neighbor No supportNo Neighbor API in v0.2.0.Let users choose peers per neighborhood, issue per-napplet addresses, route events and blobs, and revoke access across reconnects. Production sizing assumes one working transport on both platforms. FIPS interoperability also requires an iOS peer connection and event exchange with Myco.Proposal
Production, one transportXL 500k–900k
Two-phone LAN prototypeM 100k–250k
FIPS + Myco interoperabilityXXL 900k–2M+
mesh No supportHistorical, withdrawn proposal. Experimental LAN code is present but unavailable to napplets in ordinary builds.Hypothetical completion of the withdrawn draft would integrate paired LAN components in ordinary builds and verify pairing, delivery, forwarding and revocation on devices.Mesh implementation guideProposal
L 250k–500k
value No supportNo value-transfer or zap API.Integrate one wallet backend for quotes, approval, sending and status. Recover interrupted payments without paying twice when the first outcome is unknown.Proposal
XL 500k–900k
pow No supportNo proof-of-work API.Implement queued, cancellable proof-of-work jobs with progress, pause, resume and approved publication. Test battery use and foreground transitions on devices.Proposal
M 100k–250k
blossom No supportBlossom reads and uploads are available through resource and upload. The standalone Blossom API is unavailable.Extend existing verified reads and approved uploads with standalone endpoints, server lists, authorization and blob management, including deletion.Proposal
L 250k–500k
hashtree No supportNo standalone API.Resolve mutable roots, verify and traverse trees, read and write files, publish roots and manage pins, transfers and jobs. Assumes a reusable HTS-01 library.Proposal
XL 500k–900k
fs No supportNo standalone API.Implement a virtual filesystem with scoped paths, atomic writes, revisions, watches and consent for shared or destructive changes.Proposal
L 250k–500k
torrent No supportNo standalone API.Embed a torrent engine on both platforms. Add retained jobs, file selection, verified range reads, seeding, recovery and storage controls.Proposal
XXL 900k–2M+
nzb No supportNo standalone API.Integrate an external downloader, queue, history and job controls. Authorize access to completed output separately. An embedded Usenet engine would add scope.Proposal
M 100k–250k
soulseek No supportNo standalone API.Integrate a reusable Soulseek engine for search, peer browsing, downloads, transfer controls and bounded access to completed files.Proposal
XL 500k–900k
git No supportNo standalone API.Integrate scoped repository handles and object reads. The estimate includes writes and publication. The five required read and lifetime operations would take less work.Proposal
XL 500k–900k
catalog No supportNo napplet-facing API.Expose the existing verified catalogue as a read-only snapshot. Return opaque IDs that select the same publisher and handler in Intent.Proposal
S 40k–100k
count No supportNo napplet-facing API.Add relay filter counts, distinguish an unavailable count from zero and avoid counting the same result twice across sources.Proposal
S 40k–100k
dm No supportNo napplet-facing API.Integrate one encrypted messaging protocol end to end, including history, sending, live delivery, account-isolated storage and relay recovery.Proposal
XL 500k–900k
email No supportNo napplet-facing API.Implement accounts, credentials, mailbox and thread reads, composition and sending. Give reader and composer napplets separate grants.Proposal
XL 500k–900k
lists No supportNo napplet-facing API.Extend follow-list mutation to NIP-51 and NIP-65 lists. Preserve unrelated entries and relay markers, then recheck the latest list before signing.Proposal
M 100k–250k
navigation No supportNo napplet-facing API.Keep per-instance history of committed intent locations. Replay Back and Forward to the same instance and reconcile the location it reports.Proposal
M 100k–250k
ble No supportNo napplet-facing API.Add device selection, scoped GATT sessions, service discovery, reads, writes, notifications and teardown. Test real peripherals on both platforms.Proposal
L 250k–500k
capture No supportNo napplet-facing API.Add microphone consent, native recording, bounded encoded output, cancellation and teardown on interruption or account change. Test physical microphones on both platforms.Proposal
M 100k–250k
display No supportNo napplet-facing API.Integrate one documented display backend. Enumerate devices, issue opaque IDs, translate logical RGB updates and handle disconnects.Proposal
M 100k–250k
gamepad No supportNo napplet-facing API.Route physical controller input through the shell to the focused napplet. Test connection changes and focus transfers with real controllers.Proposal
M 100k–250k
location No supportNo napplet-facing API.Mediate coarse, precise and background access separately. Reconcile OS permissions and grants and enforce the restriction on direct WebView geolocation.Proposal
L 250k–500k
motion No supportNo napplet-facing API.Mediate native sensor sampling with permission and focus checks. Verify that unfocused frames cannot keep reading sensors directly.Proposal
M 100k–250k
serial No supportNo napplet-facing API.Implement device selection, open, read, write, close, permissions and disconnect recovery. Assumes a chosen accessory with a viable transport on both platforms.Proposal
L 250k–500k
webrtc No supportNo napplet-facing API.Implement shell-owned sessions and Nostr signaling for negotiation, send, receive and termination. Test two devices across different networks.Proposal
L 250k–500k
llm No supportNo napplet-facing API.Integrate one hosted model provider, shell-owned credentials, prompt-disclosure consent, generation, partial results and cancellation.Proposal
M 100k–250k
system No supportNo napplet-facing API.Expose scoped diagnostics for capabilities, services, relays, cache and media. Verify isolation of each napplet’s private state.Proposal
S 40k–100k
webmcp No supportNo napplet-facing API.Let a napplet register tools for an authorized agent. Add consumer authorization, attribution, schema validation, invocation, progress and cancellation.Proposal
L 250k–500k
worker No supportNo napplet-facing API. Local browser workers are available separately.Add runtime-owned worker creation, isolated execution, ordered messaging, termination and cleanup.Worker policyProposal
M 100k–250k
class No supportThis deferred domain is unavailable.Settle how the deferred class proposal fits current manifests and grants, then implement posture assignment and reporting. Sizing assumes a settled contract.Proposal
M 100k–250k
connect No supportThis deferred domain is unavailable.Resolve the class model, then enforce reviewed per-origin grants for fetch, sockets and event streams. Verify revocation and isolation in both WebViews.Proposal
XL 500k–900k

Support was reviewed against v0.2.0 on 20 November 2026. Each audited row links to the release code and the draft revision used.Release support reportNAP registryUpstream proposals