RefractorSpace

Pending transactions storage and multisig aggregator for Stellar Network.

   
Category Governance Tools
Website https://refractor.space
App Repository https://github.com/stellar-expert/refractor
SignerInspector Repository https://github.com/stellar-expert/stellar-tx-signers-inspector
First Released March 2021
Intake https://github.com/SCF-Public-Goods-Maintenance/scf-public-goods-maintenance.github.io/issues/26
Budget Requested 25,500
Maintenance Reserve 2,000
Other 23,500

Project Description

Refractor is a pending transactions storage and multisig aggregator for Stellar Network.

It’s a developer-focused service in the first place, but anyone can use it to store transactions and gather signatures required to match the signing threshold. Users can explicitly set expiration date and custom callback URL. Refractor automatically discovers potential signers and computes the thresholds, ensuring that signatures are valid and consistent.

Other services and wallets can access and sign a transaction using a standard URL where its hash serves as a unique identifier. The website displays current signing status, suitable signers, and thresholds. Any eligible signer can sign the transaction. As soon as it reaches the required threshold (calculated automatically), the service either submits the transaction to Stellar network or executes a callback.

Team & Experience

Refractor is maintained by the StellarExpert team. We build infrastructure tools on Stellar since 2016. Our notable projects: StellarExpert, Reflector, StellarBroker, Albedo, LedgersTax.

Active developers of the Refractor service:

Retroactive Impact

Our service is actively used by Aquarius DAO, Reflector DAO, YieldBlox DAO, Stratum, and other services. We have several new integrations. Currently discussing an option to add Refractor to the dapp explorer with the Freighter team. According to our logs, the service reached the SLA of 99.994% since the beginning of 2026.

Past Deliverables

2026 Q2

  • We revamped the website home page with a focus on key product features (available here: https://refractor.space)
  • The webiste now highlights various usage scenarios and contains a simple step-by-step explanation of how it works.
  • API infrastructure has been moved to a new dedicated server to provide more room for the database growth.
  • Refractor now supports 6 new extension-based wallets in the signing interface: Bitget, ForDeFi, CactusLink, Hana, Klever, OneKey, Rabet.
  • Server-side aggregator, website, and all dependency libs updated to support the upcoming Stellar protocol upgrade.

2026 Q3

  • The automatic signer scheme detection algorithm has been reviewed and extended to fully account for Soroban transaction authorization entries, so the required signers for smart contract invocations are now identified correctly. Our signature scheme discovery algorithm has been reworked to analyze and aggregate signatures for Soroban authorization entries. It also autodetects authorization entries requirements inside transactions wrapped with FeeBumpTransaction.
  • Signer detection now properly handles CAP-0071-01 (delegated authentication for custom accounts) and CAP-0071-02 (address-bound Soroban address credentials). Delegated authentication supports parsing of SorobanAddressCredentialsWithDelegates + SOROBAN_CREDENTIALS_ADDRESS_V2 and recursive authentication resolution tree.
  • The transaction analyzer follows ledger entry sponsorship changes and associated signature requirements. In addition, it produces warnings for invalid/malformed sponsorship transactions (missing EndSponsorshipOp, mismatched sponsorship recepient, etc).
  • We added direct WalletConnect integration and reworked the signing UX to better support mobile wallets flow. Freighter and Albedo are available through direct shortcuts, other wallet that support WalletConnect can sign a transaction either through QR code scan or direct wc:// protocol link.

Incomplete deliverable:

  • Allow adding signatures for SIGNER_KEY_TYPE_HASH_X and SIGNER_KEY_TYPE_ED25519 directly from the interface without wallet invocation ($1000).

Proposed Impact

We aim to improve the website, documentation, provide relevant usage examples, and perform some direct outreach to Stellar developers community to showcase how they can streamline their complex multisig workflows using our service. This may significantly simplify life for any developers that have to deal with multi-party controlled wallets, preauthorized transactions, or escrow services backed by by Stellar.

Proposed Deliverables

  • Allow adding signatures for SIGNER_KEY_TYPE_HASH_X and SIGNER_KEY_TYPE_ED25519 directly from the interface without wallet invocation ($1000)
  • Add a preview block to the “Upload transaction” page. It should display extended transaction information before the transaction is uploaded and processed on the server side: whether all potential signer accounts exist on-chain, whether the transaction is valid, whether it has already been uploaded or executed, the expiration date and minimum execution date (if set), and the full list of signers. ($2000)
  • In addition to pasting transaction XDR, allow uploading binary XDR files, as well as SEP-7 and Stellar Lab-formatted links. ($600)
  • Add a new simulation interface that allows simulating signatures and checking whether a specific set of signatures allows submitting a transaction to the network. ($2000)
  • Add a “Send test callback” function to the uploaded transaction so that users can check their server-side transaction handling code. ($1000)
  • Add interfaces for uploading and processing (signing) Soroban auth entries separately from transactions. The interfaces will be significantly different, since an auth entry doesn’t have timebounds, cannot contain some signer types (like HashX), and cannot be submitted to the network. The unique auth entry ID will be derived from the hash of its contents. ($7000)
  • Display a detailed activity trail for a transaction: when it was uploaded to Refractor, when it was first signed, when the last signature was added, and when it was submitted to the network. ($3000)
  • Provide a more user-friendly description of transaction contents so that signers understand exactly what they are signing: display the protocol name for known smart contract calls, highlight addresses that match signers (transfer to/from one of the signers), and mark potentially dangerous operations. Show a short summary of the transaction in the title instead of the hash. ($6000)
  • Display decoded transaction submission results: ledger, fee charged, and per-operation result codes. ($500)
  • Add a sharing widget to the transaction page with a QR code and a direct link to copy. ($200)
  • Introduce additional transaction XDR actions: “Download”, “Open in Stellar Lab”. ($200)

Maintenance Reserve: $2,000. Covers hosting costs, protocol updates, and all on-going bug fixes.

Metrics loaded from PG Atlas

PG Atlas 90d Contributors Pony Factor Adoption

  • As the project representative, I agree to the Legal Acknowledgements.

Back to top

This site uses Just the Docs, a documentation theme for Jekyll.