Refractor is a pending transaction storage
and multisig aggregator for Stellar Network.
Refractor analyses every source account, detects eligible signers, and computes threshold based on their weights.
Signatures are gathered and merged server-side, avoiding concurrent-signing conflicts and submission errors. Every signature is validated.
Store any pending transaction at no cost. Once uploaded it's lives there until it is fully singed and executed.
Share a direct web link where anyone can sign using any Stellar wallet — with live signing status and thresholds.
Do not sign transactions blindly, see what's inside in details. Detailed operation descriptions ensure that you can make confident decisions.
Use callback URLs to handle signed transactions, plug in external services, or send notifications as soon as they are ready.
Painless and straightforward transaction signing experience even for users without sufficient technical expertise.
Use Refractor in your projects through API integration. Originally built for multisig-based governance, it can facilitate many other use cases.
Require N-of-M executive sign-off (e.g., CFO + 2 directors) for outgoing payments from the corporate vault.
Elected or token-weighted signers control fund disbursement, with off-chain governance voting.
Distribute signer keys across several key holders or air-gapped devices in different geographic locations, none of which alone meets the signing threshold.
Classic 2-of-3 setup where the arbiter only needs to co-sign in a dispute.
Fractional owners as signers with weights proportional to ownership stake.
Require both an operational signer and a compliance officer signer for asset issuance or freezing actions.
Hash a future transaction and add it as a signer, enabling trustless conditional execution (e.g., atomic swaps, scheduled disbursement) with hashed proofs.
Require confirmation from a second device or hardware key added as a signer, so a compromised phone alone can't move funds.
Trustees each hold a signer, with weights reflecting fiduciary role, enforcing joint sign-off per fund governance rules.
Compose your transaction, then store it on Refractor. Just choose the network (Stellar Pubnet and Testnet supported), set an expiration date, and decide whether it should be submitted automatically once signed. Want to plug in some automation? Set a callback URL that will received a fully signed transaction.
Refractor generates a unique link for your based on the transaction hash (e.g. refractor.space/tx/3da4…e981). Just share it with your co-signers and that's it — our service will take of the rest. No need to coordinate who exactly should sign the transaction and in what order. Refractor can analyze a configured multisig scheme and determine eligible signers automatically.
Eligible key holders can sign a proposed transaction using any Stellar wallet. Refractor validates each signature, and tracks progress against the calculated signing threshold. Without this a transaction will fail if it contains not enough signatures or more than required (yes, you heard it right, a transaction with too much signatures will be discarded by Stellar). All invalid, malformed, duplicate, or excessive signatures get rejected.
The moment the required threshold is reached, Refractor either submits the transaction to the Stellar network or fires your custom callback depending on settings.
Anyone with the link can view transaction details, so avoid storing anything that could enable front-running or leak private information.
A transaction source account must exist on-chain before transaction upload to ensure proper signers and weights retrieval.
Autosubmit doesn't ensure strictly sequential ledger inclusion. Set timebounds on interdependent transactions when order matters.