-
Notifications
You must be signed in to change notification settings - Fork 1
Dev to Main #86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Dev to Main #86
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Do not merge this state into PRD!
TaprootFreak
requested changes
Nov 13, 2025
Contributor
TaprootFreak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merge blocked until Citrea is finally ready
* [DEV-4458] Update infrastructure * [DEV-4458] Changes after review * [DEV-4458] Change because of renaming compose file * [DEV-4458] Add second volume again
* [DEV-4476] Citrea monitoring * [DEV-4476] Changed env to EVM_WALLET_SEED
Added L-BTC to deferredClaimSymbols array in both dev and prod configurations to enable server-side automatic claiming for L-BTC swaps.
Only cBTC should be in the deferred claim symbols list.
* [NO-TASK]: Rewrite request to Boltz claim server * Rename path
* Remove RBTC/RSK support from Boltz configuration - Remove BTC/RBTC swap pair - Remove RSK network configuration and contracts - Focus on BTC, cBTC, and USDT stablecoin swaps only * Fix USDT_CITREA contract address Use correct JUSD token contract on Citrea Testnet: - Old: 0x1Dd3057888944ff1f914626aB4BD47Dc8b6285Fe - New: 0xFdB0a83d94CD65151148a131167Eb499Cb85d015 * Rename USDT_CITREA to JUSD_CITREA The token on Citrea Testnet is Juice Dollar (JUSD), not USDT. Rename symbol to reflect the actual token name.
Document Layer0 and Lightning.space integration for JUSD peg arbitrage: - Layer0 bridge contracts (USDT, USDC, WBTC) between Ethereum and Citrea - Lightning.space atomic swap contracts and endpoints - StablecoinBridge architecture for USDT.e to JUSD conversion - Complete arbitrage loop explanation - All contract addresses and fee structures
* Increase stablecoin chain swap max from 1000 to 10000 USDT Affects dev.lightning.space pairs: - USDT_ETH ↔ JUSD_CITREA - USDT_POLYGON ↔ JUSD_CITREA * Also increase prd stablecoin swap limit to 10,000 USDT Sync stablecoin limits between dev and prd configs: - USDT_ETH ↔ USDT_CITREA: 1,000 → 10,000 USDT - USDT_POLYGON ↔ USDT_CITREA: 1,000 → 10,000 USDT
… config (#99) * Add USDC swap pairs for Ethereum only Add USDC support for Ethereum <-> Citrea swaps: Tokens added: - USDC_ETH (0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48) - USDC_CITREA (0xE045e6c36cF77FAA2CfB54466D71A3aEF7bBE839) Swap pairs added: - USDC_ETH <-> USDC_CITREA (prd) - USDC_ETH <-> JUSD_CITREA (dev) Limits: 1-10,000 USDC (same as USDT after PR #97) Polygon USDC NOT supported due to bridge incompatibility: - Polygon Bridge creates USDC.e (bridged) - Native USDC uses different contract address * Fix USDT swap limits in documentation (1,000 -> 10,000) * Set all swap fees to 0% * Remove RBTC/RSK (Rootstock) swap configuration * Change all stablecoin swaps to exclusively use JUSD * Prepare PRD config for Citrea Mainnet (placeholders for missing addresses) * Fix token decimals: JUSD=18, cBTC=18 (EVM native tokens) * Revert cBTC decimals change - cBTC uses satoshi units like BTC
* Add Boltz PostgreSQL debug endpoint - Add new endpoint POST /support/debug/boltz for querying Boltz PostgreSQL - Same security as MSSQL debug endpoint (SQL AST parsing, column blocking) - Blocked columns: referrals.apiKey/apiSecret, keyproviders.privateKey, *.preimage - Blocked schemas: pg_catalog, information_schema, pg_toast - Add boltz-debug.sh shell script for CLI access - Add pg dependency for PostgreSQL connection - Requires BOLTZ_PG_* environment variables for configuration * Fix Boltz blocked columns config - Remove non-existent keyproviders table (actual table is 'keys' with no sensitive data) - Add dblink functions to blocked list (external DB connections) * Fix PostgreSQL case-sensitivity in script examples PostgreSQL tables reverseSwaps and chainSwaps require double quotes due to camelCase naming. Updated script help text with correct quoting examples and clarified config comment. * Add missing blocked column and dangerous function - Block minerFeeInvoicePreimage in reverseSwaps table - Block pg_sleep function to prevent DoS attacks
TaprootFreak
approved these changes
Jan 25, 2026
…103) * Add WBTC token and WBTC/cBTC swap pair - Add WBTC token to Ethereum configuration (both DEV and PRD) - Add WBTC/cBTC swap pair for Ethereum WBTC <-> Citrea cBTC swaps - WBTC contract: 0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599 * Fix WBTC swap pair: use WBTCe_CITREA instead of cBTC - Change swap pair from WBTC/cBTC to WBTC/WBTCe_CITREA (PRD only) - Add WBTCe_CITREA token on Citrea with contract 0xDF240DC08B0FdaD1d93b74d5048871232f6BEA3d - Remove WBTC configuration from dev-boltz.conf (PRD only feature) * Rename WBTC to WBTC_ETH for naming consistency * Update JUSD_CITREA contract address for testnet --------- Co-authored-by: TaprootFreak <142087526+TaprootFreak@users.noreply.github.com>
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not merge this state into PRD!