Frequently asked questions

What is the difference between a transfer and a withdrawal?

In short, withdrawals require quorum approval and transfers do not. Transfers are also more configurable, specifically with how network fees are charged. Transfers also allow you to queue up as many transfers from the same wallet as you would like (assuming sufficient funds).

Please see our transfers and transactions sections for more information.

If I want to limit withdrawals via API to only trusted destinations, how do I do this?

Currently, all external withdrawal requests made via API and in the iOS app have to go through quorum approval and Anchorage Digital risk review. Users have the ability to add “trusted destinations” and should notify their client experience manager to note that all transfers to non-approved destinations should be rejected.

Do I need to use my real data and ID information for onboarding and completing sandbox KYC?

In order to complete onboarding to sandbox, you must complete the KYC form sent to you. If you’ve entered sensitive information you would like redacted, please contact [email protected].

In production, all onboarded users for an organization will undergo full KYC in order to access the Anchorage Digital iOS app and web dashboard.

I’ve submitted my onboarding video after scanning my QR code, but it’s stuck on Anchorage Digital review. What should I do?

Once you have submitted your video for sandbox onboarding, Anchorage Digital will review and approve the request. If your account has not been approved within an hour, please contact your Anchorage Digital point of contact for sandbox onboarding via email or directly via Slack.

What devices do you support? Can I still access the sandbox without an iPhone?

We only support iOS devices—iPhones and iPads—at this time, due to the secure enclave within these devices. Unfortunately without an iPhone, you will not be able to access the sandbox app, web dashboard, or member quorum. However, you will still be able to call our APIs, using the keys created and shared with your team during onboarding.

What devices do you support? Can I still access the sandbox without an iPhone? (cont.)

Device security is critical to safeguarding customer accounts and signing on-chain transactions using mobile devices. If other devices release similar functionality, we will re-evaluate supporting additional devices at that time. Listed below are the iOS devices we currently support:

• iPhone 8, 8 Plus, X, XS, XS Max, XR, 11, 11 Pro, 11 Pro Max, SE (2nd gen), 12, 12 Pro, 12 mini, 13, 13 Pro, 13 mini.
• iPad (5th gen and later), mini 4, mini (5th and 6th gen), Air 2, Air (3rd and 4th gen), Pro (all versions).

How do I add a new user to my organization?

To gain access to the TestFlight app, please have the new member contact your main point of contact at Anchorage Digital. Once you have the app installed, an admin member of the account needs to follow the below steps to generate a QR code for each user to scan:

• Tap the gear icon ⚙️ at the lower right-hand corner of the app and tap users.
• Tap add icon ➕ at the top right-hand corner of the app.
• Follow the prompts to set policies/vaults.
• Share the unique QR code with the new users.
• If you are not in the same physical place, the admin can take a screenshot of the QR code and email it to you.

The new users will then have to:

• Scan the QR code in the Anchorage Digital iOS app.
• Input preliminary KYC information, including basic personal data, voice, and biometric training.
• Wait for quorum approval in the waiting screen.

The admin who initiated the request will then be prompted to submit biometric approval via their iOS device. For the initial batch of users in sandbox, this will be the Anchorage Digital team. Once approved, other quorum members will receive a push notification that the operation needs approval.

A second approver will then be required to submit their approval. Finally, Anchorage Digital compliance will then review the new user’s personal identifiable information (PII) and accept the request after completing due diligence.

What is the API host URL used for your APIs?

• Production: [https://api.anchorage.com/v2]
• Sandbox: [https://api.anchorage-staging.com/v2]

How do I generate a signature for signing my API calls? Do you have any scripts to help with this?

• See our reference client page

How do you decide when an API needs to be signed with a signing key?

The default is to require a signature, but the exceptions are read-only endpoints. Signatures are optional unless explicitly required, but are encouraged for all requests. If a signature is provided, it will be verified. Note that certain endpoints require an ED25519 signature to be provided alongside the API key. These endpoints will specify the Api-Signature and Api-Timestamp headers as additional parameters.

Are asset symbols in sandbox different from production?

Yes. The assets used in sandbox are on their own testnets. For example, we use asset type “BTC_T” (testnet asset) in sandbox, but use “BTC” (mainnet asset) in production.

What if I lose my device or my device is stolen?

Inform your client experience manager at Anchorage Digital. The phone will be marked as "lost" in the app, and Anchorage Digital will deactivate the lost phone. When you purchase a new phone, your team will be able to help you recover access easily. Please contact Anchorage Digital for support.

Can I revoke my API key if it is compromised?

In the event that your organization deems that a key has either been compromised or stored incorrectly and you would like to revoke access, you are able to do so using the web dashboard or by emailing [email protected].

Once an API key has been revoked, it cannot be reinstated and a new key will need to be created. If you would like to create a new key using a previously created permission group, you do not need a quorum approval or risk review. To do this, go to the API section of your web dashboard, select the three dots icon, and select Revoke.

Please note that only admin users with the correct access credentials can revoke API keys. Anyone with access to the account—admin, member, view-only—can see details regarding permission groups and past keys created. However, users will not be able to see the actual, hexadecimal API key.

What is a quorum?

Quorums are important as they allow us to authenticate organizational intent—to make sure that the transactions initiated align with the governing structure of your organization. Thus, quorums are an important part of our processes at Anchorage Digital, both internally and for our end users.

What role do quorums play in onboarding?

When we onboard a new client, they’re required to have a minimum of three admins. All initial individuals onboarded are admins. From there, new users can be added, new vaults can be established, and new policies can be set through a quorum of admins.

Do all transactions require quorum?

All transactions require a valid quorum of unique and unforgeable cryptographic signatures from multiple client organization members. Quorums are configurable per vault and can be configured to require any M of N.

For example, in a hypothetical company where there are five distinct employees that require the ability to transfer funds, a common configuration would be to have three of the five approve any given transaction. Clients may also specify a required user for any quorum, and may use different sets of users and different quorum settings per vault within a given account.