AitvarasCONFIDENTIAL SERVICES
Signers, bots, gas stations, and protection services. Run them in your infrastructure. Start with AWS Nitro.
14 services
Network agnostic
An enclave sample that signs approved text payloads with an ephemeral key.
The local AWS Nitro sample uses P-384 and is not an Ethereum transaction signer. Runtime attestation and durable key recovery are not implemented.
Ethereum
Policy-controlled signing for apps on Ethereum.
Proposed AWS Nitro target. Compatible signing code, chain configuration, policy rules, key recovery, and a reviewed deployment adapter still need to be implemented and tested. No hosted deployment is available.
Arbitrum
Policy-controlled signing for apps on Arbitrum.
Proposed AWS Nitro target. Compatible signing code, chain configuration, policy rules, key recovery, and a reviewed deployment adapter still need to be implemented and tested. No hosted deployment is available.
Base
Policy-controlled signing for apps on Base.
Proposed AWS Nitro target. Compatible signing code, chain configuration, policy rules, key recovery, and a reviewed deployment adapter still need to be implemented and tested. No hosted deployment is available.
Reya
Policy-controlled signing for apps on Reya.
Proposed AWS Nitro target. Compatible signing code, chain configuration, policy rules, key recovery, and a reviewed deployment adapter still need to be implemented and tested. No hosted deployment is available.
Network agnostic
Distributed signing with independent participants and a defined approval quorum.
A proposed integration, not an implemented MPC protocol. Participant separation, supported curves, quorum, key-share recovery, and network compatibility require validation. Multiple replicas of a single-node signer do not create MPC.
Canton
A proposed signing integration for Canton applications.
Proposed AWS Nitro target. The request format, key lifecycle, authorization model, compatibility, and deployment adapter require validation before launch.
Network compatibility private
Licensed signer packages supplied privately by your organization.
AWS Nitro integration candidate. Network and protocol compatibility are not declared publicly. No package, source, or implementation details are published here. Customer entitlement and independent verification are required before deployment.
Ethereum · Arbitrum · Base · Reya
Run a trading strategy with a separate signer and policy-controlled execution.
Proposed targets only. A strategy implementation, market-data connections, venue integration, signing service, exposure limits, and tested recovery are required. No trading automation is deployed by the catalog.
Ethereum · Arbitrum · Base · Reya
Monitor eligible positions and execute liquidations within configured limits.
Proposed targets only. Lending-protocol adapters, position monitoring, capital configuration, signer integration, transaction simulation, and failure handling need implementation and testing.
Ethereum · Arbitrum · Base · Reya
Sponsor or fund transaction fees under organization limits and approval rules.
Proposed targets only. Funding or sponsorship adapters, supported transaction formats, signer integration, abuse controls, budgets, and reconciliation require implementation and testing.
Network agnostic
Check requests against permissions, approval rules, and transaction limits.
The separate service is planned. A policy contract, identity checks, audit records, and enforced integration with a signer or automation worker are needed. The local signer sample's policy checks do not implement this catalog service.
Network agnostic
Evaluate exposure and suspicious activity before a service executes a request.
A proposed service. Data sources, risk models, thresholds, intervention behavior, and integration contracts require implementation and validation. Confidential execution alone does not establish risk protection.
Network agnostic
Bring your container or EIF package and declare what it needs to run.
Private uploads are available today, including packages for other institutional services. The pilot runtime is AWS Nitro; compatible packaging and a reviewed adapter are needed to run a service. Uploading records a receipt and does not deploy it.
Cloud and network tags describe targets, not verified deployment compatibility. Planned and private integrations cannot be launched from the hosted catalog.
BRING YOUR OWN SERVICE
Package your service with its configuration, dependencies, and enclave evidence. Client apps connect to the services you run.