Artax

Use the left navigation to move between review, account, pricing, and setup pages.

Compatibility

See what wallets and launch paths we have actually tested.

This page summarizes Artax wallet, browser, and signing-path coverage, plus the checks behind each profile. It shows tested combinations clearly and calls out gaps just as clearly. Production certification requires an explicit certification grant.

Tested combinationsLaunch checksBrowser and wallet matrixNo production support badge

Compatibility records and known limits

Artax publishes a compatibility matrix, supporting checks for each profile, launch-readiness notes, and explicit browser, wallet, signing-path, and partner rows. That keeps the current view clear: core launch paths, partial evidence, example surfaces, limited launchers, and automation coverage are all shown separately. None of that is a production certification grant by itself.

Compatibility profiles

Wallet, surface, and signing-path profiles recorded in the compatibility matrix.

Certification records

Each compatibility profile links to certification evidence.

Formal matrix rows

Browser, wallet, signing-path, and partner rows documented here.

Automation checks

Explicit certification checks linked back to release evidence and compatibility profiles.

Evidence-backed

Profiles with enough evidence for guarded validation.

3/4

Launch prep

Profiles closest to live release approval.

2/4

Production certified

Profiles granted production compatibility certification.

0/4

What this page can say

What this page can promise

Public certification evidence

Allowed today.

Production certification claims

Not available.

Most verified path

1 profile(s) link to devnet evidence, 3 profile(s) link to pre-production evidence, and 2 profile(s) are marked for launch preparation. That is narrower than a production certification grant.

Formal matrix coverage

4 of 4 compatibility profile(s) have formal browser-wallet, signing-path, or partner-surface matrix rows. Coverage stays explicit, even where scope is example-only or limited.

Non-blocking surfaces

2 profile(s) stay example-only or limited-scope so they do not blur the supported core paths.

Freshness warnings

4 certification record(s) and 4 formal matrix row(s) are past review cadence.

Why this exists

This registry publishes the current compatibility-certification evidence posture and blockers for current Artax surfaces. It does not mark any current profile as production certified.

What still is not true

This page does not certify universal wallet or browser support, end-to-end embedded signing ownership, or production readiness.

Current compatibility profiles

These cards show the matrix status next to the supporting checks for each profile. The goal is simple: keep the visible compatibility story aligned with real evidence and real blockers.

web_hosted_review_browser_wallet_adapter

browser wallet through the hosted Artax web review flow

Matrix status

Implemented Not Formally Certified

Certification evidence status

Formal Matrix Repo Ui And Staging Smoke Evidence (review overdue)

Readiness evidence

Staging Hardened Launch Window Candidate (evidence-backed) (launch candidate)

Launch scope

Core Launch Path

Current scope

Current hosted-review browser-wallet launch path only. This is not a universal wallet-brand, browser-family, or embedded-signing certification statement.

Current readiness scope

Current hosted-review browser-wallet launch behavior is hardened enough to stay in the production-ready staging milestone and eventual launch window, while still remaining narrower than broad browser-family or wallet-brand production certification.

Formal matrix rows

browser_wallet.web_hosted_review.wallet_standard (Certified With Conditions)

Related flows

SPL token transfer review and submit

Current surfaces

/review page; /hosted-review page

Environments

repo; local; staging

Release evidence

Monorepo CI validation (Implemented Initial); Public web-edge staging smoke verification (Implemented Initial); Render staging rollout workflow (Implemented Initial)

Launch gates

gate.flow.spl_token_transfer_review_and_submit (Local And Devnet Verified Not Production); gate.release_target.render_staging_rollout (Staging Rollout Gated Not Production)

Automated certification checks

Repo monorepo build and validation baseline (Repo Build And Validation Only); Local production-like runtime contract verification (Local Runtime Contract); Staging hosted-review web-edge smoke (Staging Web Edge Smoke)

Current blockers

Formal browser-wallet matrix exists, but runtime browser and wallet coverage is still limited to the current repo, local, and staging checks.; Guarded production rollout and smoke paths now exist, and formal attestation and release-attestation-artifact policies now exist alongside release-approval-authority, release-promotion, release-smoke-verification, and release-rollback policies, and first checked-in local or synthetic proof production records now exist across attestation, authority, promotion, smoke-verification, and rollback-target families, but no live workflow-backed production evidence or signed provenance record exists yet.

Still needed before launch

This profile has enough evidence for guarded launch validation.

Still needed before production

Broaden browser-level runtime certification beyond the current hosted-review path.; Bind the path to live production canary, smoke, and signed release evidence.; Keep support language narrower than generic wallet-brand or browser-family claims until explicit production certification exists.

Still outside scope

No embedded wallet ownership or full in-app signing support is certified here.; No generic browser-wallet brand claim is allowed from this record.

api_server_to_server_review_submit

server-to-server review and submit with external wallet signing

Matrix status

Implemented Not Formally Certified

Certification evidence status

Formal Matrix Repo Devnet And Staging Linked Evidence (review overdue)

Readiness evidence

Staging Hardened Launch Window Candidate (evidence-backed) (launch candidate)

Launch scope

Core Launch Path

Current scope

Current server-to-server review and submit path with externally owned wallet signing. Integrator-specific signing behavior remains explicitly scoped and uncertified beyond this narrow path.

Current readiness scope

Current server-to-server review and submit with external wallet signing is hardened enough for the production-ready staging milestone and launch-window planning, but it still remains narrower than broad signing-path production certification.

Formal matrix rows

signing_path.api_server_to_server.external_wallet_signature (Certified With Conditions)

Related flows

SPL token transfer review and submit; Transfer sponsorship Class A simple transfer; Transfer sponsorship Class B recipient account setup; Transfer sponsorship Class C wrapped SOL setup; Transfer sponsorship Class D bounded wrapped SOL principal shortfall; Simple swap review

Current surfaces

POST /api/analyze-transfer; POST /api/analyze-swap; POST /api/submit-transfer; POST /api/submit-transaction; @artax/sdk

Environments

repo; local; devnet; staging

Release evidence

Monorepo CI validation (Implemented Initial); Local production-like Docker rehearsal (Implemented Initial); Live devnet verification workflow (Implemented Initial); Render staging rollout workflow (Implemented Initial)

Launch gates

gate.flow.spl_token_transfer_review_and_submit (Local And Devnet Verified Not Production); gate.flow.transfer_sponsorship_class_d_bounded_principal (Local And Devnet Verified Not Production); gate.flow.simple_swap_review (Local And Devnet Review Only Not Production); gate.surface.sdk_package (Implemented Not Production Certified); gate.release_target.render_staging_rollout (Staging Rollout Gated Not Production)

Automated certification checks

Repo monorepo build and validation baseline (Repo Build And Validation Only); Local production-like runtime contract verification (Local Runtime Contract); Live devnet submit verification for the current server rail (Live Devnet Submit Verification); Staging rollout gate for current public API and web surfaces (Staging Rollout Gate)

Current blockers

Formal signing-path matrix exists, but automated certification still covers only the current narrow external-wallet server-to-server path.; Guarded production-candidate and production rollout workflows now exist, and formal attestation and release-attestation-artifact policies now exist alongside release-approval-authority, release-promotion, release-smoke-verification, and release-rollback policies, and first checked-in local or synthetic proof production records now exist across attestation, authority, promotion, smoke-verification, and rollback-target families, but no live workflow-backed production evidence, production approval, or signed provenance record exists yet.

Still needed before launch

This profile has enough evidence for guarded launch validation.

Still needed before production

Convert current local, devnet, and staging evidence into live production release evidence.; Broaden automated certification for more signing-path edge cases such as partial-signature preservation and prompt-order regressions.; Bind the path to production approval, signed provenance, and live canary evidence.

Still outside scope

This record does not certify generic wallet-adapter behavior outside the explicit server-to-server rail.; Swap review remains narrower than transfer submission because sponsorship stays unsupported and submit evidence is optional on devnet.

partner_demo_embedded_review_no_signing

embedded review without embedded signing ownership

Matrix status

Implemented Example Only

Certification evidence status

Formal Partner Matrix Repo Example Surface Only (review overdue)

Readiness evidence

Example Only Non Launch Blocking

Launch scope

Example Only Non Launch Blocking

Current scope

Current partner demo and UI package examples only. This is a design and integration example surface, not a production compatibility certification for embedded signing ownership.

Current readiness scope

Current partner demo embedded review remains a repo-scoped design and integration example. It does not need to be staging-ready for the core launch window as long as public language stays example-only.

Formal matrix rows

partner_surface.embedded_review.partner_demo_no_signing (Experimental)

Related flows

None

Current surfaces

partner demo app; @artax/ui

Environments

repo

Release evidence

Monorepo CI validation (Implemented Initial); Generated provenance baseline for build and rollout inputs (Implemented Initial)

Launch gates

gate.surface.sdk_package (Implemented Not Production Certified); gate.surface.partner_demo_embedded_review_example (Implemented Example Surface Not Production)

Automated certification checks

Repo monorepo build and validation baseline (Repo Build And Validation Only); Repo partner demo embedded review contract check (Repo Embedded Review Contract)

Current blockers

This surface remains intentionally example-only and does not yet carry staging rollout or partner production evidence.; No dedicated partner launch evidence or broader partner support contract exists yet.

Still needed before launch

Decide whether the partner demo should remain example-only or graduate into a launch-scoped partner surface.; Add staging/runtime certification and rollout evidence if broader partner support is ever claimed.

Still needed before production

Keep the surface documented as example-only unless the broader partner-support program is funded and certified.

Still outside scope

The partner app still owns the connected wallet.; No embedded signing or production partner rollout is certified from this record.

extension_hosted_review_launcher

browser extension popup review with trusted launch helpers and active-tab wallet signing bridge

Matrix status

Preview Popup Review Not Formally Certified

Certification evidence status

Formal Matrix Popup Review Preview With Runtime Acceptance Export (review overdue)

Readiness evidence

Preview Surface Staging Verified Non Launch Blocking (evidence-backed)

Launch scope

Preview Only Non Launch Blocking

Current scope

Current browser extension fast-trust popup behavior only, including trusted partner launch, active-tab wallet linking, popup review, and popup submit when the narrow contract passes. This does not certify any universal signing overlay or generic browser-wallet compatibility.

Current readiness scope

Current extension behavior remains a preview popup-review surface with a trusted-launch bridge and active-tab wallet link, but the runtime lab can now export a trusted acceptance snapshot from local or staging after the popup flow is exercised. The surface stays non-launch-blocking and narrower than universal signing claims.

Formal matrix rows

browser_wallet.extension_launcher.link_out (Experimental)

Related flows

SPL token transfer review and submit

Current surfaces

browser extension popup review

Environments

repo; local; staging

Release evidence

Monorepo CI validation (Implemented Initial); Extension popup runtime acceptance export (Implemented Initial)

Launch gates

gate.surface.extension_launcher (Preview Surface With Runtime Acceptance Evidence Not Certified)

Automated certification checks

Repo monorepo build and validation baseline (Repo Build And Validation Only); Repo extension popup-review contract check (Repo Popup Review Contract); Extension popup-review runtime acceptance snapshot validation (Staging Popup Runtime Acceptance Export)

Current blockers

Formal browser-wallet matrix plus runtime acceptance export now exist for popup review and active-tab wallet-bridge behavior, but certification remains experimental, preview-only, and narrower than broad browser-wallet support.; The extension surface remains preview-only and intentionally narrower than generic browser-wallet or universal interception language.

Still needed before launch

This profile has enough evidence for guarded launch validation.

Still needed before production

Keep the surface documented as preview-only unless browser-device runtime evidence broadens the claim.; Replace manual acceptance exports with broader staged and production runtime evidence before widening support language.; Bind any broader extension-support claim to stronger browser-device certification and production launch-gate evidence.

Still outside scope

Popup review plus active-tab wallet bridge is the only supported extension scope today.; No universal signing overlay claim is allowed.

What counts as certification input today

Repo source evidence

Each profile links back to real tests, files, or checks.

Formal certification matrices

2 browser-wallet row(s), 1 signing-path row(s), and 1 partner-surface row(s) capture the hosted-review, popup-review, server-submission, and embedded-review combinations instead of leaving them implicit.

Automation coverage

8 explicit checks tie the profile rows back to builds, local runtime checks, devnet submissions, and guarded rollout evidence.

What evidence still is not

None of these records grant production certification. They are evidence summaries, launch-readiness signals, matrix rows, and blockers.

What still must happen before production support language

Stronger runtime coverage

The matrices now exist, but browser-family, device, wallet-brand, and signing-edge coverage still needs wider testing.

Launch boundary

Some example or limited-scope surfaces are intentionally non-blocking. Readiness should be judged on the core launch paths, not by treating every surface as equally critical.

Production release evidence

Pre-production rollout evidence is useful, but it is not a production rollout workflow or a production release gate.

Partner and extension depth

The partner demo has its own matrix row and contract check, but it is still an example; the add-on remains a limited popup-review surface rather than a universal signing overlay.

Narrow public language

Until those pieces exist, Artax docs, trust surfaces, and examples must stay narrower than universal compatibility or production-support claims.

Read next

Trust

See how trust surfaces stay narrower than compatibility certification and production support.

Open

Read next

Release assurance

Inspect the release evidence and launch checks behind production support language.

Open

Read next

Benchmarks

Compare benchmark evidence with compatibility evidence without treating either as superiority proof.

Open

Read next

Developers

Inspect the API, SDK, hosted-review, and embedded-review entry points these compatibility records refer to.

Open

Read next

Quickstart

Follow the setup flow without mistaking convenience for broad compatibility certification.

Open

Read next

Comparisons

Read the comparison guide that stays anchored to the compatibility checks on this page.

Open