XLMUSDT
Stellar Lumens / Tether USD
cryptoComposite

The XLM memo stayed in my instructions after I read Bell's W proposal

TLDR: Templar launches Precept, an institutional lending protocol on Stellar where each market configures its own collateral, borrow assets, risk parameters, and price feeds. Three launch markets go live today: XLM/USDC, deJAAA/USDC, and Gami earnUSDC/USDC. DeFindex and Re7 join as launch partners and curators. Guardian audited the protocol with no critical findings.

Hey r/Stellar, I've been building **Lazarus Protocol**, an open-source, decentralized state-rent and footprint TTL keeper network for Soroban smart contracts. **The problem**: Every persistent storage entry, contract instance, and WASM bytecode on Soroban has a TTL counter. When it hits zero, it gets evicted from active validator RAM into cold archive storage (CAP-0062). While Protocol 23 added reactive restoration (CAP-0066), the first user who touches an expired entry gets hit with up to a 10x fee spike and for shared DeFi state (AMM pools, lending reserves, oracle registries), no single user has an incentive to pay upkeep. Right now, every team has to run private cron servers with hot keys just to keep their state warm. **How Lazarus works:** Because Stellar Core only allows a single operation per Soroban transaction envelope, you can't bundle an ExtendFootprintTTLOp with an InvokeHostFunctionOp to pay a keeper inline. Lazarus solves this using a **Decoupled Voucher Pattern**: 1. dApps register their contract and deposit USDC/XLM escrow into lazarus\_vault. 2. Independent keeper nodes pack up to 100 expiring storage keys into ExtendFootprintTTLOp transactions before they expire. 3. Our hybrid indexer (Stellar Hubble BigQuery + RPC getLedgers stream) verifies the on-chain extension and issues a domain-separated Ed25519 voucher. 4. Keepers redeem vouchers in batches (\`record\_bump\_batch\`) from the vault contract to claim bounties. Links (Live on Stellar Testnet): Web Console: [https://lazarusprotocol.online](https://lazarusprotocol.online) GitHub: [https://github.com/LazarusProtocol](https://github.com/LazarusProtocol) Vault Contract: **CBKFA2F7RUDGLJNE3K5X2XEXVXRJQ5AMB2NSPREDTATE2ZHDALFKPGUR** Would love any feedback from other Soroban builders

Hbar, Algo, XLM