FAQ

What is Hinkal WaaS?

Hinkal Wallet-as-a-Service (WaaS) is a managed wallet infrastructure that allows organizations to create wallets, manage users, define permissions, and execute private blockchain transactions through a REST API.

Who should use Hinkal WaaS?

Organizations building payroll systems, exchanges, treasury platforms, payment applications, embedded finance products, and enterprise blockchain solutions.

How is WaaS different from the Hinkal API?

With the API, users keep and control their own wallets. With WaaS, wallets are generated and managed inside Hinkal's secure enclave.

How is WaaS different from the SDK?

The SDK is designed for self-custody integrations. WaaS is designed for managed wallet environments.

Which chains does WaaS support?

Ethereum, Solana, Tron, and supported EVM-compatible chains.

Does WaaS support multiple chains?

Yes.

What wallet types can WaaS create?

EVM, Solana, and Tron wallets.

Does every wallet include all supported chains?

Yes.

What is an Organization?

The top-level entity used to manage users, wallets, and permissions.

Why do I need an Organization?

Organizations provide access control and management capabilities.

Can I create multiple Organizations?

Yes.

What is a User?

An identity within an Organization.

Can an Organization have multiple Users?

Yes.

Can Users have different permissions?

Yes.

What is a Policy?

A permission rule that controls what actions a user can perform.

Why are Policies required?

To prevent unauthorized operations.

Can Policies be updated?

Yes.

Can Policies be removed?

Yes.

What actions can Policies control?

Wallet creation, transaction signing, administration, and other supported actions.

What is the minimum setup flow?

Create Organization, Create User, Grant Policies, Create Wallet.

Can Organization creation be automated?

Yes.

Can User creation be automated?

Yes.

Can Wallet creation be automated?

Yes.

Does WaaS require manual user interaction?

Not necessarily.

Can wallets be created programmatically?

Yes.

How are users identified?

By Ed25519 public keys.

Does WaaS use passwords?

No.

Does WaaS use email authentication?

No.

Does WaaS use API keys?

No.

What authentication method does WaaS use?

X-Stamp authentication.

What is X-Stamp?

An Ed25519-based request signing mechanism.

Why does WaaS use X-Stamp?

To provide cryptographic authentication without passwords.

What is required for every request?

A valid X-Stamp signature and unique nonce.

What is a nonce?

A unique value included in every signed request.

Why is a nonce required?

To prevent replay attacks.

What happens if a nonce is reused?

The request is rejected.

Can I generate my own Ed25519 keypair?

Yes.

Should keypairs be generated locally?

Yes.

Does Hinkal generate authentication keys?

No.

Does Hinkal store authentication private keys?

No.

How should I store my private key?

Securely using your infrastructure or key management system.

Can authentication keys be rotated?

Yes.

Can users have different keypairs?

Yes.

What happens if I lose my private key?

You must generate and register a new keypair.

What is a root user?

The first administrative user created within an Organization.

How do I create my first Organization?

Generate a keypair and call the organization creation endpoint.

Can the root user manage all users?

Yes.

Can the root user create policies?

Yes.

Can the root user create wallets?

Yes.

Can the root user sign transactions?

Yes, if policies permit.

What permissions are required to create wallets?

CREATE_WALLET.

What permissions are required to sign transactions?

SIGN_TRANSACTION.

Why am I getting a policy error?

The user lacks permission for the requested action.

Can policies grant administrative access?

Yes.

Can policies be assigned to multiple users?

Yes.

Can policies be revoked?

Yes.

Where are wallet private keys generated?

Inside the secure enclave.

Can database administrators access wallet private keys?

No.

Can cloud providers access wallet private keys?

No.

Are wallet private keys encrypted?

Yes.

How are wallet keys protected?

They are generated, stored, decrypted, and used only inside the enclave.

What is a secure enclave?

A hardware-isolated environment for sensitive operations.

Does transaction signing happen inside the enclave?

Yes.

Can developers export wallet private keys?

No.

Can organizations export wallet private keys?

No.

Can organizations import existing wallets?

No.

Does the enclave store decrypted keys?

No.

What happens if the API server is compromised?

Wallet keys remain protected by the enclave.

Can administrators view wallet private keys?

No.

Can administrators export wallet private keys?

No.

Can administrators create users?

Yes.

Can administrators create wallets?

Yes.

Can administrators execute transactions?

Yes, if policies allow.

Does WaaS support role-based access control?

Yes.

Can I retrieve wallet addresses?

Yes.

Can I retrieve organization information?

Yes.

Can I retrieve user information?

Yes.

Can I retrieve wallet information?

Yes.

Can I retrieve balances?

Yes.

Does WaaS support deposits?

Yes.

Does WaaS support withdrawals?

Yes.

Does WaaS support transfers?

Yes.

Does WaaS support swaps?

Yes.

Does WaaS support Public→Public transactions?

Yes.

Does WaaS support Public→Private transactions?

Yes.

Does WaaS support Private→Private transactions?

Yes.

Does WaaS support Private→Public transactions?

Yes.

Can WaaS perform batch payouts?

Yes.

Can WaaS be used for payroll?

Yes.

Can WaaS be used for treasury management?

Yes.

Can WaaS be used for payment processing?

Yes.

Can I estimate transaction fees?

Yes.

What fees apply to WaaS transactions?

Network fees and applicable Hinkal service fees.

Does WaaS support compliance workflows?

Yes.

Does WaaS support selective disclosure?

Yes.

Does WaaS share the same security model as the Hinkal API?

Yes.

Does WaaS use the same enclave infrastructure as the Hinkal API?

Yes.

What information should I provide when reporting a WaaS issue?

Provide Organization ID, User ID, wallet address, chain ID, endpoint used, request payload, error message, transaction hash (if applicable), and timestamp.