Common Tasks

This document is to document the engineering teams process and procedures to provide clarity into the regular and irregular activities that we perform. These tasks typically come through #engineering-requests in slack

Common Engineering Requests

Temporary: Preventing a User from Logging In

After a request has been sent to freeze a user, and this request has been approved by, the engineer performing the task will: Add “+frozen” to the user’s email domain: i.e. “jake@gmail.com” -> “jake@gmail.com+frozen” Set the password to a random string Enable 2fa and set the 2fa secret to a random string

This was a bit of a one off / first time I’ve done this, but two wallets were made for an IRA account and the user deposited to the wrong wallet. (Link) Switch name of wallets (Melanie Kalnins Vault <> Melanie Kalnins Traditional IRA - Heritage IRA) Switch subtype of wallets (STANDARD <> TRADITIONAL_IRA)

IRA account not being prompted to sign a Bitgo agreement

This is intentionally designed this way. Only individual accounts are prompted to sign BitGo agreements as they go through B2B2C. This might have changed since the feature was launched because we weren't onboarding (m)any IRAs. So we might need to reevaluate this code and sync with operations on how they are using that account type. (Link) Switched account to INDIVIDUAL from ROTH_IRA

Update Stripe Payment Method

Occasionally, ops will generate a link in Stripe to allow the customer to create a billing method. If they do this, engineering needs to login to Stripe to get details Update the account stripePaymentId field to be the payment id, starts with “pm_” Update the account stripePaymentType to be the payment type, usually card or link

Adding a BitGo trust ID

Update the bitgoTradingEnterpriseId to the desired value on the account

Adding Tetra xpubs

Add xpubs to xpubs array at packages/database/src/migrations/2026-0331-add-tetra-xpubs Run script with NEXT_PUBLIC_VERCEL_ENV=production and DATABASE_URL=””