Squads Multisig: Step-by-Step Verification

Limited tooling is available for Solana verification compared to EVM. Exercise extra caution and cross-verify with team members.

Authored by:

Isaac Patka

SEAL | Shield3

Geoffrey Arone

Shield3

Louis Marquenet

Opsek

Pablo Sabbatella

SEAL | Opsek

Dickson Wu

SEAL

Reviewed by:

Piña

Coinspect

engn33r

Workflow

1. Initial Proposal (SOL transfer, token transfer, signer/threshold change)

2. Simulation

• Squads UI provides a simulation link after first signature
• Simulation is helpful for transfers; configuration changes often fail, but you can still inspect data via explorer

SOL Transfer Verification

Transaction Link Simulation Link

On the simulation page scroll down to System Program Instruction This shows the destination address for the SOL (H2p…Kr) and the Instruction Data. The instruction data can be interpreted as follows.

02 00 00 00 80 96 98 00 00 00 00 00

1. Split into bytes: 02 00 00 00 80 96 98 00 00 00 00 00
2. First 4 bytes (transfer type): 02 00 00 00 = [2, 0, 0, 0] ✅ (confirms this is a token transfer)
3. Amount bytes (little-endian): 80 96 98 00 00 00 00 00 = [128, 150, 152, 0, 0, 0, 0, 0] in decimal
4. Convert from little-endian to decimal:
   • Little-endian means least significant byte first
   • 80 96 98 00 = 0x00989680 in big-endian hex
   • 0x00989680 = 10,000,000 in decimal
5. Convert lamports to SOL:
   • 1 SOL = 1,000,000,000 lamports
   • 10,000,000 lamports ÷ 1,000,000,000 = 0.01 SOL ✅

Quick verification method: For the amount portion (80 96 98 00 00 00 00 00):

• Reverse the order: 00 00 00 00 00 98 96 80
• Convert hex to decimal: 0x989680 = 10,000,000
• Divide by 1,000,000,000: 10,000,000 ÷ 1,000,000,000 = 0.01 SOL

USDS Transfer Verification

Transaction Link Simulation Link)

On the simulation page scroll down to Associated Token Program: Create Idempotent & Token Program Instruction This shows the destination address for the USDS in the Token Program Instruction (H2p…Kr) and the Instruction Data. The instruction data can be interpreted as follows.

0c 40 42 0f 00 00 00 00 00 00 06

1. Split into bytes: 0c 40 42 0f 00 00 00 00 00 00 06
2. First byte (instruction type): 0c = 12 in decimal ✅ (confirms this is TransferChecked instruction)
3. Amount bytes (little-endian): 40 42 0f 00 00 00 00 00 = [64, 66, 15, 0, 0, 0, 0, 0] in decimal
4. Convert from little-endian to decimal:
   • 40 42 0f 00 = 0x000f4240 in big-endian hex
   • 0x000f4240 = 1,000,000 in decimal
5. Convert raw units to USDS:
   • USDS has 6 decimals
   • 1,000,000 raw units ÷ 10^6 = 1.0 USDS ✅
6. Decimals verification: Last byte 06 = 6 decimals ✅ (correct for USDS)

Configuration Change Verification

Transaction Link Simulation does NOT seem to work for configuration changes, but we have another way we can verify it!

1. Copy the transaction ID (4KDPpv27fQmbWteQjSZLku8sGxNfoDqtYG4mZQp2zbiq)
   1. This will take you to an 'account' page on the Solana explorer representing just this transaction
2. Click the first transaction in the history of this 'transaction account'
3. Scroll down to Squads Multisig Program: Config Transaction Create
   1. Expand all fields to view the decoded transaction data

Signing & Execution

• Sign (do not execute) and confirm expected hash on Ledger
• Execute after collecting all signatures
• Once all signatures are collected, execute the transaction.