Sandbox testing

Validate the complete MicroVault lifecycle on Ethereum Sepolia.

Use https://sandbox.groundtech.co, chain ID 11155111, and Sepolia USDC for this test plan.

Prerequisites

• A sandbox organization with MicroVaults enabled
• An active vault created through the quickstart
• An external test wallet with Sepolia USDC and enough Sepolia ETH for wallet-signed transactions
• The vault’s VAULT_ID

export GROUND_API="https://sandbox.groundtech.co"
export GROUND_API_KEY="..."
export AUTH="Authorization: Bearer $GROUND_API_KEY"
export VAULT_ID="d9902b20-6499-4465-a4c3-5d2208182f79"

1. Record the starting state

Save the vault, source positions, and activity before moving assets. This gives each later balance change a known baseline.

curl -sS "$GROUND_API/v2/microvaults/vaults/$VAULT_ID" -H "$AUTH" | jq
curl -sS "$GROUND_API/v2/microvaults/vaults/$VAULT_ID/sources" -H "$AUTH" | jq
curl -sS "$GROUND_API/v2/microvaults/vaults/$VAULT_ID/activity" -H "$AUTH" | jq

2. Test synchronous flows

1. Approve the test wallet.
2. Complete a first subscription, then repeat it with a second amount.
3. Set a strategy that moves assets into a synchronous source and wait for the rebalance to complete.
4. Request a redemption preview. When its mode is instant, submit it and verify that USDC reaches the wallet in the same transaction.

After each transaction, compare the wallet receipt with the latest activity and vault balances.

For a subscription, verify that wallet USDC decreases by the deposited amount, the share balance increases, and total assets increase by the same base-asset amount before strategy movement. For an instant redemption, verify that shares decrease and the receiver’s USDC increases in the same transaction.

3. Test an asynchronous redemption

Allocate assets to an asynchronous source, request a redemption preview, and verify that its mode is requested. The preview should identify the source exits and show expected timing when available.

Submit the request, wait until activity reports it as claimable, and then claim the USDC from the test wallet. Confirm that the redemption becomes completed only after the claim transaction succeeds.

While it is pending, verify that total assets still account for assets in flight and that source progress identifies the liquidation being performed. When it becomes claimable, verify the actual proceeds and fixed receiving address before submitting the claim.

4. Test controls and retries

• Remove a shareholder and verify that the wallet can no longer obtain an active proof.
• Set a source to each supported mode and verify that entry and exit follow the mode table in Configure strategy and source modes.
• Retry an API request with the same idempotency key and identical body; verify that it returns the original operation rather than creating another one.
• Retry the same key with a different body; verify that the request is rejected.

Test authority export in the Ground Portal last because Ground-managed configuration stops after the export confirms.

Confirm the test run

A complete run has confirmed activity for both subscriptions, the tested rebalances, the immediate redemption, and the requested redemption plus claim. Reconcile the final wallet USDC and share balances with the vault’s total assets, idle assets, source positions, and redemption liabilities.

If a transaction receipt succeeds but the expected activity does not appear, keep the transaction hash and request ID, refresh the relevant read endpoint, and do not repeat the write until its status is known. If an operation reaches a failed state, correct its reported cause and retry with a new idempotency key.