Orion

eng @SquadsLabs | building blocks @ParagonStaking | passkeys @getbunkr

[Orion @BasedOrion_]

Milestone: Running a Node ✅

Super proud to say that @BGuillaumat_ and I are running a validator (@ParagonStaking) together ❤️

Supporting the network I use 24/7 feels like such a full circle moment 🙌

Feel free to follow or stake while we work towards our leader slot 🫂

[Orion @BasedOrion_]

@cavemanloverboy @toly Baller shit

[Orion @BasedOrion_]

@watchking69 Valid questions if you don’t have history/relationship with that dealer

Honest business is great and all, but far from guaranteed

[Orion @BasedOrion_]

@0x_febo Lfg 🙌🤝

[Squads @multisig]

Announcing Solana Multisig Tools

Three new open-source tools for Squads Protocol v4.

All three are small, self-hostable, and built with minimal dependencies. We're actively engaging with STRIDE to help strengthen multisig management practices on Solana. This is the first step towards multiple independent frontends and access points to v4.

multisig-cli

A focused Rust CLI for reviewing, simulating, signing, and executing multisig proposals. It parses multisig accounts and instructions directly instead of pulling in a large dependency tree. The result is a binary that's easy to audit and well suited for high-trust operational workflows.

If you're using an older CLI, we recommend switching to this multisig-cli which has minimal dependencies.

multisig-verifier

A static, zero-backend browser UI. Reads multisigs state directly from Solana RPCs, decodes proposals, tracks approvals, and lets members approve or reject from their own wallet. No secrets leave the browser. Strict CSP rules by default.

multisig-monitor

Real-time visibility into multisig activity. Watches configured multisigs, decodes actions, and emits notifications when members create, vote on, execute, or modify configuration. Treasury and governance events surface as they happen.

The pattern across all three: inspect before signing, verify before approving, monitor after execution.

Smaller dependency surfaces reduce supply-chain risk. Direct decoding reduces blind signing. Open implementations are reviewable end-to-end. Monitoring closes the loop.

We strongly encourage every team to verify what they're signing through more than one interface. Don't rely solely on any single frontend. Cross-check with a CLI, an independent verifier, or a second client before approving anything that matters.

We're working with a number of security teams who will host their own versions of the multisig-verifier. You can self-host today. Soon teams will also be able to access independently operated instances run by parties with no affiliation to Squads.

Link to the repo in the post below.

[Orion @BasedOrion_]

@L0STE_

[Orion @BasedOrion_]

@jnwng @SolanaFndn @solana Absolutely generational run 🙏🫶

[Stepan | squads.xyz @SimkinStepan]

An update on what we're focusing on with @multisig in light of the Drift incident last week.

What we're building now:

1. A proxy program for v4 that lets you opt in to killing durable nonces for a specific signer. This removes the ability for pre-signed transactions to sit indefinitely waiting to be executed.

2. A dedicated protocol management multisig program with configurable template policies and a UI you can run locally. Built for teams that need tighter governance controls over admin operations.

3. Exploring clear signing with intents so signers can verify exactly what a transaction does before approving it (cc @Redacted_Noah).

What's already available on v4 and can be set up by your team today:

– Timelocks. You can set these up in Settings. They create a mandatory delay between proposal approval and execution.

– Signer permissions. You can assign Propose, Vote, and Execute rights separately, so not every signer has the same level of access.

– Multisig nesting. You can set up configurations where eg two separate multisigs are signers on a third. Adding a layer of operational separation.

-Minimal UI. An interface on top of v4 that you can run locally (https://t.co/sUSZcnV4OI).

If you're unsure about your current setup or want guidance on how to configure any of this, DM us.

[Orion @BasedOrion_]

@redacted_noah @ansel_sol @SimkinStepan

[Orion @BasedOrion_]

@ansel_sol @redacted_noah @SimkinStepan Just saw the parent post, seems this might be outdated?

[Orion @BasedOrion_]

In essence I thinks its rooted in the right idea, but under all the current wallet standards/offerings, the clear intent signing advantage would only apply to CLI + "hot" wallet signing.

Ledgers etc still rely on showing you hashes rather than the actually "clear" tx or message underneath.

So at least for mission critical actions people take with custodians & ledgers etc, jobs not finished 🥲

[Orion @BasedOrion_]

Super cool to see this kind of stuff being spun up 🙌

Kudos @gumsays 🫶

[Orion @BasedOrion_]

@gumsays If you ever need help parsing or anything of the sort, DM 🫡

[Orion @BasedOrion_]

@trentdotsol @L0STE_ say less

[Orion @BasedOrion_]

@toly @TheSoftwareJedi @trentdotsol @SimkinStepan Yeah we’re currently thinking through options on how to block & constrain behavior specifically around durable nonces

[Altitude @altitude]

SWIFT transfers are live.

Pay any bank account, anywhere in the world. Directly from your Altitude account.

200 countries. 11,000 banks. 1 balance.

[Orion @BasedOrion_]

IBRL’ing on the mountain

[Orion @BasedOrion_]

@alessandrod Granted would probably be a better look to land settlement faster by adding tiny prio fee & budget ixn….

[Orion @BasedOrion_]

@alessandrod Make raw transactions great again

[Orion @BasedOrion_]

@redacted_noah Just to feel something every once in a while

[Orion @BasedOrion_]

@heymike777 @multisig Paying transaction fees natively from the vault sadly isn’t possible due to how Solana works.

What exactly are you trying to achieve?