{"meta":{"source":"https://stellarlight.xyz/ideas","generatedAt":"2026-11-08T23:55:52.077Z","filters":{"q":null,"category":null,"quarter":null,"status":null,"limit":100,"offset":0},"counts":{"total":16,"open":0,"closed":16,"matched":17,"returned":17,"syntheticRounds":1},"countBasis":"total/open/closed = curated RFP briefs only. matched/returned = result rows, which ALSO include synthetic 'scf-round' rows (rowType: 'scf-round', synthetic: true) representing the live SCF round's open submission window. To count or render briefs, filter rowType === 'rfp'; round context is also in meta.scfRound.","activeQuarter":"q4-2026","activeQuarterLabel":"Q4 2026","briefRoster":{"source":"https://stellar.gitbook.io/scf-handbook/scf-awards/build-award/rfp-track","checkedOn":"2026-11-04"},"scfRound":{"currentRound":46,"currentPhase":"Submission","lastConfirmedRound":45,"lastConfirmedRoundNote":"In progress: SCF #46 (Submission, submission deadline 2026-11-09). SCF #45 is the last concluded round.","submissionWindow":{"opens":null,"closes":"2026-11-09"},"roundsInProgress":[{"round":46,"phase":"Submission","submissionDeadline":"2026-11-09"}],"asOf":"2026-11-08","source":"live","verifyAt":"https://communityfund.stellar.org/awards"},"categories":[{"value":"ai","label":"AI"},{"value":"consumer-dapps","label":"Consumer dApps"},{"value":"defi","label":"DeFi"},{"value":"developer-tooling","label":"Developer Tooling"},{"value":"gaming","label":"Gaming"},{"value":"infrastructure","label":"Infrastructure"},{"value":"nfts","label":"NFTs"},{"value":"payments","label":"Payments"},{"value":"scf","label":"SCF"},{"value":"web3-social","label":"Web3 Social"}],"quarters":[{"value":"q1-2026","label":"Q1 2026"},{"value":"q2-2026","label":"Q2 2026"},{"value":"q3-2026","label":"Q3 2026"},{"value":"q4-2026","label":"Q4 2026"}],"submitNewBriefAt":"https://stellarlight.xyz/ideas"},"funding":"Stellar Community Fund (SCF): these briefs say what the ecosystem wants built. `open` means the brief is still soliciting; whether SCF accepts a proposal TODAY depends on the round state in meta.scfRound (submissionWindow, currentPhase, roundsInProgress), dated by asOf. Closed briefs are past rounds, surfaced for context.","rfps":[{"id":"scf-round-46","title":"SCF Round #46: submissions OPEN until 2026-11-09","description":"Stellar Community Fund round #46 is currently accepting submissions (deadline 2026-11-09). The Build Award funds Stellar/Soroban projects: eligibility, rules and the application flow are in the SCF Handbook (https://stellar.gitbook.io/scf-handbook). Apply via https://communityfund.stellar.org.","technicalRequirements":null,"category":"scf","authorName":"Stellar Community Fund","quarter":"q4-2026","categoryLabel":"SCF","quarterLabel":"Live round","status":"open","url":"https://communityfund.stellar.org/awards","rowType":"scf-round","synthetic":true},{"id":"prices-api","title":"Prices API & Indexing Service","description":"The Stellar ecosystem lacks a single, reliable, and standardized API to source aggregated, real-time, and historical price data for all Stellar assets (Classic and SEP-41 Soroban tokens). This fragmentation hinders the development of accurate DeFi protocols, portfolio tracking tools, and general-purpose applications, significantly increasing integration complexity for builders.","technicalRequirements":"Asset Coverage: Full support for all current native Stellar assets and SEP-41 Soroban contract tokens.\n\nPrice Aggregation: Algorithm to calculate weighted average prices across major on-chain (Soroswap, Aquarius, SDEX, Blend) and off-chain markets.\n\nVolume Weighting (VWAP): Inclusion of a configurable USD-denominated trading volume threshold for market inclusion to filter out illiquid pairs.\n\nData Endpoints: Delivery of real-time price endpoints and historical price endpoints for intervals including 24h, 7d, 30d, and 1yr.\n\nPerformance: High availability, low-latency architecture capable of handling high query volumes.","category":"infrastructure","authorName":"Jake","quarter":"q1-2026","publishedBrief":{"title":"Prices API","url":"https://github.com/stellar/scf-handbook/blob/be0c693d89a0990d9fabebc61fd2894d23ec55e2/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Infrastructure","quarterLabel":"Q1 2026","status":"closed","url":"https://stellarlight.xyz/ideas/prices-api","rowType":"rfp","synthetic":false},{"id":"defi-positions-api","title":"DeFi Positions API","description":"As the Stellar DeFi sector matures with protocols like Blend and Aquarius, users and developers face significant complexity in tracking aggregated positions. There is currently no unified way to view deposits, borrowings, and yield across disparate protocols, leading to a fragmented user experience.","technicalRequirements":"Protocol Support: Initial integration with top-tier DeFi protocols by TVL (e.g., Blend, Aquarius, FxDAO).\n\nProtocol Semantics: Integration of protocol-specific logic, such as Blend's backstop pools or varied collateral/interest models.\n\nPosition Data Points: API must return deposited and borrowed amounts, current interest rates / APY (for both deposits and loans), total yield earned and full position history.\n\nUser Input: Support for both Stellar G-addresses and Soroban C-addresses.","category":"defi","authorName":"Jake","quarter":"q1-2026","publishedBrief":{"title":"DeFi Positions API","url":"https://github.com/stellar/scf-handbook/blob/be0c693d89a0990d9fabebc61fd2894d23ec55e2/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"DeFi","quarterLabel":"Q1 2026","status":"closed","url":"https://stellarlight.xyz/ideas/defi-positions-api","rowType":"rfp","synthetic":false},{"id":"c-address-tooling","title":"C-Address Tooling & Onboarding","description":"The shift to C-addresses (Soroban smart accounts) faces two major adoption blockers: the friction of needing a G-address to fund a C-address, and a lack of modern mobile SDKs for the Smart Account standard.","technicalRequirements":"G-to-C Seamless Bridge: A protocol or service enabling direct funding of C-addresses via G-addresses, CEX withdrawals, or fiat-to-crypto proxy services.\n\nTransparent UX: The funding mechanism should aim to make the G-address requirement transparent or unnecessary for the end-user.\n\nStakeholder Integration: Must consider the specific integration needs of existing Stellar wallets.","category":"infrastructure","authorName":"Tyler","quarter":"q1-2026","publishedBrief":{"title":"C-Address Tooling & Onboarding","url":"https://github.com/stellar/scf-handbook/blob/be0c693d89a0990d9fabebc61fd2894d23ec55e2/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Infrastructure","quarterLabel":"Q1 2026","status":"closed","url":"https://stellarlight.xyz/ideas/c-address-tooling","rowType":"rfp","synthetic":false},{"id":"soroban-block-explorer","title":"Soroban-First Block Explorer","description":"Most existing Stellar explorers prioritize classic assets. The lack of deep, legible support for Soroban transactions prevents developers and users from consistently verifying contract interactions, hindering the growth of DeFi and collectibles.","technicalRequirements":"SEP-41 Indexing: Development of high-quality, open-source libraries (React Native, Swift, Kotlin) implementing the OZ smart account standard.\n\nHuman-Readable Transactions: UI must translate complex contract interactions into clear, legible actions rather than raw hex data.\n\nEvent Handling: Full support for CAP-67 events and SEP-41 transaction handling.","category":"infrastructure","authorName":"Keeks","quarter":"q1-2026","publishedBrief":{"title":"Soroban-first Block Explorer","url":"https://github.com/stellar/scf-handbook/blob/be0c693d89a0990d9fabebc61fd2894d23ec55e2/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Infrastructure","quarterLabel":"Q1 2026","status":"closed","url":"https://stellarlight.xyz/ideas/soroban-block-explorer","rowType":"rfp","synthetic":false},{"id":"concentrated-liquidity-amm","title":"Advanced AMM Framework (Concentrated Liquidity)","description":"Current Stellar AMMs primarily use constant-product models. This uniform liquidity distribution leads to inefficient capital usage. The ecosystem needs a standardized framework for concentrated liquidity to enable tighter spreads and more expressive market structures.","technicalRequirements":"Concentrated Liquidity: Smart contract implementation allowing LPs to provide liquidity within specific price ranges.\n\nPosition Management: Support for position-based liquidity and robust LP accounting.\n\nEfficiency: High-performance swap execution and automated fee calculations.\n\nExtensibility: Modular architecture to support future \"hooks,\" custom fee models, or specialized pool logic.","category":"defi","authorName":"Ishan","quarter":"q1-2026","categoryLabel":"DeFi","quarterLabel":"Q1 2026","status":"closed","url":"https://stellarlight.xyz/ideas/concentrated-liquidity-amm","rowType":"rfp","synthetic":false},{"id":"soroban-vrf","title":"Soroban Verifiable Random Function (VRF)","description":"Soroban contracts are deterministic and lack native secure randomness. Without a VRF, on-chain games and NFT mints rely on exploitable entropy (like block timestamps), compromising security and trust.","technicalRequirements":"Cryptographic Verification: Generation of off-chain randomness with proofs (e.g., ECVRF) that can be verified on-chain at low cost.\n\nTamper Resistance: Absolute guarantee that neither node operators nor users can predict the outcome before finalization.","category":"infrastructure","authorName":"Raph","quarter":"q1-2026","categoryLabel":"Infrastructure","quarterLabel":"Q1 2026","status":"closed","url":"https://stellarlight.xyz/ideas/soroban-vrf","rowType":"rfp","synthetic":false},{"id":"reverse-engineering-tool","title":"Specialized Reverse Engineering Tool","description":"Soroban contracts are WASM files with specific internal logic. Existing decompilers produce generic code that is difficult for researchers to audit for security or optimization.","technicalRequirements":"Internal Context: The tool must incorporate specific Soroban internal knowledge to produce a more accurate WAT/C-close representation.\n\nAccuracy Benchmark: Aim for 90% accuracy in the reconstruction of decompiled WASM contracts to ensure they are human-understandable.","category":"developer-tooling","authorName":"Matej","quarter":"q1-2026","publishedBrief":{"title":"Soroban Specialized Reverse Engineering Tool","url":"https://github.com/stellar/scf-handbook/blob/be0c693d89a0990d9fabebc61fd2894d23ec55e2/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Developer Tooling","quarterLabel":"Q1 2026","status":"closed","url":"https://stellarlight.xyz/ideas/reverse-engineering-tool","rowType":"rfp","synthetic":false},{"id":"ai-webide","title":"AI-Focused WebIDE","description":"Current WebIDEs are either unmaintained or lack integrated AI. Developers currently face high costs for AI tools and a lack of environment-aware assistants that can guide them through the specific nuances of Stellar/Soroban.","technicalRequirements":"AI-First Design: Integrated AI to share code, troubleshoot, and generate Soroban-specific logic within the browser.\n\nAnalytics Driven: System should learn from user interactions to continuously improve Stellar documentation and AI suggestions.\n\nAccount Sponsoring: Mechanism to cover developer costs via \"rail-guarded\" sponsorship for Stellar-focused projects.","category":"developer-tooling","authorName":"Raph","quarter":"q1-2026","categoryLabel":"Developer Tooling","quarterLabel":"Q1 2026","status":"closed","url":"https://stellarlight.xyz/ideas/ai-webide","rowType":"rfp","synthetic":false},{"id":"hummingbot-integration","title":"Hummingbot Integration (Trading Engine)","description":"The deprecation of Kelp has left a liquidity gap. Stellar needs a bridge to the Hummingbot framework to enable automated market-making and arbitrage between Stellar and other global exchanges.","technicalRequirements":"Orderbook Support: Implementation of a Stellar orderbook connector for the official Hummingbot repository.\n\nLiquidity Provision: Enable standard market-making and arbitrage strategies.\n\nFuture Scope: (Optional) Expand to support Stellar AMMs and intra-Soroban AMM arbitrage.","category":"defi","authorName":"Rahim","quarter":"q1-2026","publishedBrief":{"title":"Hummingbot integration (open source trading engine)","url":"https://github.com/stellar/scf-handbook/blob/be0c693d89a0990d9fabebc61fd2894d23ec55e2/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"DeFi","quarterLabel":"Q1 2026","status":"closed","url":"https://stellarlight.xyz/ideas/hummingbot-integration","rowType":"rfp","synthetic":false},{"id":"trustline-onboarder","title":"Trustline Onboarder","description":"New users on Stellar must manually add trustlines before they can receive non-native assets, creating a significant friction point. There is no standardized, user-friendly flow to guide someone from receiving a payment link to holding an asset for the first time.","technicalRequirements":"One-Click Trustline: A widget or SDK that allows any app to embed a frictionless trustline creation flow.\n\nSponsorship Support: Integration with Stellar's fee and reserve sponsorship mechanisms so users can onboard without holding XLM.\n\nMulti-Asset: Support for batching multiple trustline additions in a single transaction.","category":"payments","authorName":"Tyler","quarter":"q2-2026","publishedBrief":{"title":"Trustline onboarder","url":"https://github.com/stellar/scf-handbook/blob/1e04b79973358e3dea58d821ed6419b50c93370c/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Payments","quarterLabel":"Q2 2026","status":"closed","url":"https://stellarlight.xyz/ideas/trustline-onboarder","rowType":"rfp","synthetic":false},{"id":"passkey-ui-kit","title":"Passkey UI Kit","description":"Soroban's smart account standard supports passkey-based signing, but there is no polished, reusable UI component library for wallets and dApps to integrate this experience. Teams are reinventing the same flows with inconsistent UX.","technicalRequirements":"Component Library: Pre-built React (and optionally React Native) components for passkey registration, authentication, and transaction signing.\n\nStandards Compliant: Must implement the OZ smart account standard and WebAuthn spec.\n\nCustomizable: Headless variants for teams that need full visual control.","category":"developer-tooling","authorName":"Keeks","quarter":"q2-2026","publishedBrief":{"title":"Passkey UI","url":"https://github.com/stellar/scf-handbook/blob/1e04b79973358e3dea58d821ed6419b50c93370c/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Developer Tooling","quarterLabel":"Q2 2026","status":"closed","url":"https://stellarlight.xyz/ideas/passkey-ui-kit","rowType":"rfp","synthetic":false},{"id":"account-demolisher","title":"Account Demolisher","description":"Abandoning a Stellar account requires manually removing all trustlines, offers, and data entries before merging the account; a tedious multi-step process with no tooling support. This creates UX debt for end-users and wallet developers alike.","technicalRequirements":"Automated Cleanup: Detect and batch-remove all open offers, trustlines, and account data in the minimum number of transactions.\n\nSafe Merge: Final account merge to a user-specified destination address.\n\nWallet SDK: Expose as a callable SDK function so wallets can offer \"close account\" flows natively.","category":"consumer-dapps","authorName":"Jake","quarter":"q2-2026","publishedBrief":{"title":"Account Demolisher","url":"https://github.com/stellar/scf-handbook/blob/1e04b79973358e3dea58d821ed6419b50c93370c/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Consumer dApps","quarterLabel":"Q2 2026","status":"closed","url":"https://stellarlight.xyz/ideas/account-demolisher","rowType":"rfp","synthetic":false},{"id":"contract-source-verification","title":"Contract Source Verification Service","description":"Soroban contracts are deployed as opaque WASM blobs. Without a source verification registry, users and auditors cannot confirm that the deployed bytecode matches any published source code, undermining trust in the ecosystem.","technicalRequirements":"Deterministic Build: Reproducible WASM compilation pipeline (e.g., via Docker) so source-to-bytecode matching is verifiable.\n\nRegistry API: Public API and UI to submit, verify, and query contract source code by contract ID.\n\nExplorer Integration: Hook into the Soroban-First Block Explorer (Q1 RFP) to surface verification badges.","category":"infrastructure","authorName":"Matej","quarter":"q2-2026","publishedBrief":{"title":"Contract Source Verification Service","url":"https://github.com/stellar/scf-handbook/blob/1e04b79973358e3dea58d821ed6419b50c93370c/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04","functionalRequirements":["Accepts source submissions (a tarball or equivalent) tied to a target Wasm hash.","Rebuilds the source with an SDF-allowlisted trusted build image, named by the SEP-58 bldimg field; the proposal states its image allowlist policy.","A free public API answers verification status by contract ID or Wasm hash, with the SEP-58 fields recorded (bldimg, bldopt, source_repo, source_rev, tarball_url, tarball_sha256), the linked source, build metadata, an image trust signal and a timestamp.","One shared result layer that explorers, Lab and wallets query without rebuilding; a design that makes every consumer rebuild, or rests on one hardcoded verifier, does not qualify.","Several verifiers each report against the deployed Wasm hash, and a disagreement shows per verifier, not as one status.","Covers Mainnet and Testnet.","Verifies contracts deployed before launch; retroactive verification of non-upgradable contracts is a priority.","Accepts every SEP-58 source mode: public repo (source_repo and source_rev), hosted tarball (tarball_url and tarball_sha256) and content-addressed (tarball_sha256 alone), with IPFS a first-tier channel beside HTTPS and neither HTTPS nor GitHub hardcoded; responses say which mode applies.","A CLI or developer submission flow, with the API shaped to fit stellar-cli.","Exposes verification metadata that explorers (Stellar Expert, StellarChain, Stellar Lab) and other tools can consume.","Keeps SEP-55 attestations and SEP-58 rebuild verification apart as distinct trust levels.","Aligns the API with the verifier-API SEP once that spec is written."],"outOfScope":["How each verifier chooses to display results, such as for contracts without public source.","Writing SEP-58 or SEP-55; coordination is expected.","Producing the trusted stellar-cli Docker images, which SDF maintains.","Changes to SDF-owned tools (stellar-cli, Stellar Lab) beyond exposing the APIs they consume.","UI work on any one third-party explorer.","Fully deterministic Rust compilation as a research effort: the brief asks for the best reproducibility available today, anchored on the SDF-allowlisted images."]},"categoryLabel":"Infrastructure","quarterLabel":"Q2 2026","status":"closed","url":"https://stellarlight.xyz/ideas/contract-source-verification","rowType":"rfp","synthetic":false},{"id":"oz-accounts-policy-builder","title":"OZ Accounts Policy Builder","description":"OpenZeppelin-style smart accounts on Soroban support custom signing policies, but configuring them requires writing Rust and understanding low-level contract internals. There is no no-code or low-code interface for teams to define and deploy account policies.","technicalRequirements":"Visual Policy Editor: UI for composing account policies (multisig thresholds, spending limits, time locks, allowed contracts) without writing code.\n\nCode Export: Generate auditable Rust/Soroban source from the visual policy definition.\n\nDeployment Flow: One-click deploy of the configured account contract to testnet or mainnet.","category":"developer-tooling","authorName":"Ishan","quarter":"q2-2026","publishedBrief":{"title":"OZ accounts policy builder","url":"https://github.com/stellar/scf-handbook/blob/1e04b79973358e3dea58d821ed6419b50c93370c/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Developer Tooling","quarterLabel":"Q2 2026","status":"closed","url":"https://stellarlight.xyz/ideas/oz-accounts-policy-builder","rowType":"rfp","synthetic":false},{"id":"layerzero-dvn","title":"Stellar-compatible LayerZero DVN","description":"LayerZero V2's Stellar implementation is built on Soroban and in security audits, but only one reference DVN (LzDVN, secp256k1 multisig) verifies its messages. For Stellar to be a credible omnichain destination, with issuers like USDT0, Paxos, BitGo, Solv, and Ethena preparing to launch via LayerZero, applications need a meaningful choice of independent Decentralized Verifier Networks to compose into their X-of-Y-of-N Security Stack. This RFP funds teams ALREADY operating production DVNs on LayerZero V2 to extend their service to Stellar; greenfield DVN proposals are out of scope.","technicalRequirements":"Hard Prerequisite: A production DVN live on at least one LayerZero V2 mainnet pathway, with attestation history verifiable on LayerZero Scan; the Stellar deployment is an extension of an existing service, not a new entity.\n\nStellar DVN Contract: A Soroban contract conforming to the LayerZero V2 DVN interface and the Stellar implementation's Abstract Account pattern (custom __check_auth; Soroban prohibits reentrancy), submitting attestations to Stellar's ULN302 message library. Testnet first, then an audited mainnet deployment; each team arranges and funds its own audit.\n\nOff-chain Verifier: The team's existing verification service (ZK, TEE, K-of-N, light client, or other) extended to listen to Stellar RPC for PacketSent events and attest in both directions, keeping the security guarantee consistent across pathways.\n\nStellar Constraints: Correct bytes32-to-Stellar address conversion, TTL-aware storage with the hybrid extension strategy, and attestation flows within Soroban's per-transaction limits (200 reads, instruction/memory/write-entry caps).\n\nPathway Coverage: At minimum Stellar to Ethereum, Arbitrum, Base, Optimism, Polygon, Avalanche, Solana, and BNB Chain.\n\nOperations: 24-month maintenance commitment with at least 2 nodes, public operational telemetry (verifications served, error rate, latency), and listing on LayerZero's official DVN provider directory as a hard deliverable.","category":"infrastructure","authorName":"SCF Delegates","quarter":"q3-2026","publishedBrief":{"title":"Stellar-compatible LayerZero DVN","url":"https://github.com/stellar/scf-handbook/blob/7abdddd09fe05c6de47de300a5cde73caa61cb02/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Infrastructure","quarterLabel":"Q3 2026","status":"closed","url":"https://stellarlight.xyz/ideas/layerzero-dvn","rowType":"rfp","synthetic":false},{"id":"x402-facilitator-bazaar","title":"x402 Facilitator with Bazaar Discovery","description":"x402 turns HTTP 402 into a machine-native payment flow, and Stellar suits it well: settlement costs about 0.0023 XLM, which is what makes per-request agent micropayments viable. Exact settlement already works (the Apache-2.0 @x402/stellar package and the free Built on Stellar facilitator), but Stellar has no native Bazaar, the discovery layer that lets an agent find, price, and pay for x402-protected services without a pre-existing integration. Today a Stellar-denominated service is only as discoverable as whichever multi-chain facilitator happens to carry it. This RFP funds a production facilitator on both networks plus a Stellar-native Bazaar, with discovery as the highest-value share of the budget.","technicalRequirements":"Facilitator: verify, settle, and supported on BOTH stellar:testnet and stellar:pubnet, built on @x402/stellar rather than reimplementing settlement. Strict Soroban auth-entry validation (exact call, asset, amount, recipient; no replay; ledger-based expiration), classic keypairs and custom __check_auth accounts, any SEP-41 token with USDC default and correct 7-decimal handling, sponsored network fees advertised via extra.areFeesSponsored, and strictly non-custodial.\n\nBazaar Discovery (the core new capability): GET /discovery/resources with the spec's filters and GET /discovery/search with REAL natural-language ranking; search quality is a graded deliverable. Automatic cataloging from the discovery extension with no separate registration step, HTTP endpoints and MCP tools as first-class resource types, catalog-integrity enforcement against forged listings including routeTemplate validation, and a commitment to track the moving x402 discovery conventions through the grant period.\n\nMCP Server: search and paid-call tools so an agent can discover and pay from inside a runtime, with machine-readable error codes on every rejection.\n\nupto Scheme Upstream: author scheme_upto_stellar.md and its implementation, contributed through the x402 Technical Steering Committee (SDF's Foundation board seat is available to unblock review).\n\nLicense and Conformance: a permissive OSI-approved license with no AGPL in the dependency path (the OpenZeppelin Relayer x402 plugin is AGPL and excluded as a base). Acceptance is wire-level: an unmodified canonical client completing payment end-to-end on both networks, a passing run of the x402 repo's e2e suite, and a published settled transaction hash per network per scheme.\n\nAudit: a third-party review via the Audit Bank covering the settlement path, auth-entry validation, and the discovery trust boundary before the mainnet production tag.","category":"payments","authorName":"SCF Delegates","quarter":"q3-2026","publishedBrief":{"title":"X402 Facilitator with Bazaar (discovery) support","url":"https://github.com/stellar/scf-handbook/blob/7abdddd09fe05c6de47de300a5cde73caa61cb02/scf-awards/build-award/rfp-track.md","checkedOn":"2026-11-04"},"categoryLabel":"Payments","quarterLabel":"Q3 2026","status":"closed","url":"https://stellarlight.xyz/ideas/x402-facilitator-bazaar","rowType":"rfp","synthetic":false}]}