fix: Geomi processor imports

[lndgalante]

Description

Reorder legacy event mappings so Geomi preserves the correct multisig address types during import. Add setup notes for provisioning and Hasura table tracking.

Test Plan

• Validated both configs through the cached Geomi editor.
• Confirmed mainnet transactions and owner activity in Hasura.
• Creation-candidate data still needs verification.

Next steps

The new mainnet processor has a different API URL:

https://api.mainnet.aptoslabs.com/nocode/v1/api/cmur8zfz000baqb01uqudskle/v1/graphql

Before switching the apps, let the processor catch up and verify queries using client API keys, including Hasura read permissions for all required tables.

• Web (apps/web): Update NEXT_PUBLIC_MULTISIG_INDEXER_MAINNET_ENDPOINT and configure NEXT_PUBLIC_MULTISIG_INDEXER_MAINNET_API_KEY for the new processor. Update the old schema URL in codegen.ts, run pnpm --filter web generate, and redeploy.
• Mobile (../wallet/apps/mobile): Update EXPO_PUBLIC_MULTISIG_INDEXER_MAINNET_ENDPOINT and configure EXPO_PUBLIC_MULTISIG_INDEXER_MAINNET_API_KEY in the app’s build environment, then release an updated bundle.
• Discovery in both apps: Add queries for multisig_creation_candidates. Merge the results with existing discovery, resolve successful transactions into vault addresses, deduplicate, and verify current ownership. Changing the endpoint alone won’t enable this.
• Verify the integration: Check discovery for an initial co-owner who has never voted, confirm removed owners are excluded, and check transaction history.

Keep the existing testnet configuration until its processor is migrated separately.

---

Note

Medium Risk
Changes affect deployed indexer configuration and GraphQL exposure; wrong import order or missed Hasura tracking can block processor startup or break client queries, but application runtime code is unchanged in this PR.

Overview
Fixes Geomi processor imports by reordering event mappings in multisig-mainnet.yaml and multisig-testnet.yaml so legacy *Event blocks (with account_address → multisig_account) appear before module events that map $.multisig_account. That ordering stops Geomi’s editor from rewriting shared multisig_account columns to event_metadata: account_address, which otherwise prevents the processor from starting.

The indexer README adds operational guidance: expect 5–10 minute provisioning noise, a new Hasura table tracking step (multisig_transactions, multisig_owner_activities, and mainnet multisig_creation_candidates), a Troubleshooting Processor Imports section with the required move_type: address check, and updated deployment wording to verify candidate indexing and API-key permissions before switching app endpoints.

^{Reviewed by Cursor Bugbot for commit 7aa31a5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
petra-vault-web	Ready	Preview	Oct 2, 2026 10:25pm UTC