FAQ

Frequently asked questions about Kai-Sign.

ERC7730 Compliance

Is Kai-Sign compliant with ERC7730?

Yes, Kai-Sign metadata is based on the ERC7730 standard. We have submitted metadata following the ERC7730 specification.

We've also added support for multicalls, which ERC7730 doesn't currently support. When ERC7730 adds multicall support in the future, we will update our implementation to align with the standard specification.

---

Hardware Wallet Support

Which hardware wallets are supported?

Currently, no hardware wallets are using Kai-Sign directly, but this may change in the future as hardware wallet firmware updates to support ERC7730 metadata sources like Kai-Sign.

How can I see Kai-Sign in action?

The easiest way to understand how Kai-Sign works is to use the Kai-Sign Chrome Extension. It demonstrates clear signing by showing human-readable transaction details when interacting with supported contracts.

How does the hardware viewer work?

The hardware viewer in Kai-Sign simulates how your metadata will appear on a Ledger device. It:

• Renders the exact screens users will see

• Shows formatted values (amounts, addresses, etc.)

• Helps you verify the user experience before submission

---

Integration & Development

How do I integrate Kai-Sign into my dApp?

Use the Kai-Sign API to fetch verified metadata:

// Query the subgraph for metadata
const query = `{
  specs(where: { contractAddress: "0x..." }) {
    id
    blobHash
    contractAddress
  }
}`;

See the API Documentation for details.

Is there an API available?

Yes, Kai-Sign provides:

• GraphQL Subgraph for querying metadata

• REST API for additional services

• Blob access for retrieving full metadata files

Documentation is available at beta.kaisign.xyz/api-docs.

Where are the smart contracts deployed?

Network	Address
Sepolia	0x4dFEA0C2B472a14cD052a8f9DF9f19fa5CF03719
Mainnet	Coming soon

Can I run Kai-Sign locally for development?

Yes, see the Installation Guide for setting up a local development environment with the frontend, backend, and testing tools.

---

Fees & Costs

Does it cost anything to submit metadata?

Submitting metadata involves:

• Gas fees for the on-chain transaction

• Bond amount for Reality.eth verification (refunded if your submission is validated)

What are the bonding requirements?

Reality.eth requires a minimum bond to submit or challenge metadata. Bonds are:

• Refunded if your answer is validated

• Lost if your answer is proven incorrect

• Each challenge must be at least double the previous bond

---

Troubleshooting

Why is my clear sign data not showing?

Ethereum blobs expire after approximately 18 days due to the standard blob pruning window (EIP-4844). If your metadata was submitted more than 18 days ago, the blob data may have been pruned from the network.

Solution:

• Resubmit your metadata to create a fresh blob

• Your metadata will go through the verification process again

• Blob data is also mirrored to Swarm for longer-term availability, but the primary source requires resubmission

Why was my submission rejected?

Common reasons for rejection include:

• Invalid JSON schema: Your metadata doesn't conform to the ERC7730 specification

• Incorrect contract ABI: The ABI doesn't match the deployed contract or has mismatched function selectors

• Missing required fields: Intent, labels, or format definitions are incomplete

• Malformed field paths: Path references like #.fieldName or $.metadata are incorrectly formatted

• Incorrect function selectors: The function signature doesn't match the expected selector

Review the ERC7730 specification for the complete schema requirements.

How do I update existing metadata?

Updates require a new submission. You cannot edit metadata in-place once submitted.

To update:

1. Create the corrected metadata using the Builder

2. Submit it as a new entry

3. The new submission goes through the standard verification process

4. Once verified, the new metadata will be available alongside or supersede the old entry

What multicall patterns does Kai-Sign support?

Kai-Sign extends ERC7730 with multicall support, which is not part of the base ERC7730 standard. This allows clear signing of batched transactions.

Supported patterns:

• Standard multicall aggregation (multiple calls in a single transaction)

• Each call within the multicall is decoded and displayed separately on hardware wallets

When ERC7730 adds official multicall support in the future, Kai-Sign will update to align with the standard specification.