-
Notifications
You must be signed in to change notification settings - Fork 6.2k
feat: Add Fiamma Adapter. #15805
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
feat: Add Fiamma Adapter. #15805
Conversation
The adapter at projects/fiamma exports TVL:
|
Please count the collateral held on the source chain rather than the minted tokens on the destination chain |
Fiamma Bridge locks users' Bitcoin in a Taproot script using the BitVM2 protocol, without relying on centralized custody. The unlock condition is a burn event on the sidechain, proven by a zero-knowledge proof verified within the script. Currently, there is no way to query all locked UTXOs on-chain via filtering. Users can track their own locked UTXOs through their individual transactions. In addition, Fiamma maintains a centralized record and provides a block explorer to view the locked UTXOs: https://scan.fiammalabs.io/ To make this data accessible, we can provide a centralized API endpoint that aggregates and exposes the statistics. Shall we implement such an interface? |
The adapter at projects/fiamma exports TVL:
|
Yeah please could we use the API instead and count the TVL on the source chain (bitcoin) |
The adapter at projects/fiamma exports TVL:
|
We add an api for BTC amount locked on Bitcoin. Please check again, thanks. |
So I guess all of the destination chain TVLs here are now double count of the bitcoin TVL? Can we remove them please? |
I think it's better remove bitcoin and leave others? |
No we track value locked not value issued, to be consistent with our methodology and other protocols, only bitcoin should be shown here |
The adapter at projects/fiamma exports TVL:
|
Modified. Please check again :) |
NOTE
Please enable "Allow edits by maintainers" while putting up the PR.
package-lock.json
file as part of your changes, we use lockfileVersion 2, and most use v1 and using that messes up our CIName (to be shown on DefiLlama):
Fiamma
Twitter Link:
https://x.com/Fiamma_labs
List of audit links if any:
https://github.com/fiamma-chain/fiamma-audit/blob/main/BitLabs-Bridge-script.pdf
https://github.com/fiamma-chain/fiamma-audit/blob/main/MoveBits-Bridge-Aptos-Contract.pdf
https://github.com/fiamma-chain/fiamma-audit/blob/main/Zenith-Bridge-Cairo-Contract.pdf
Website Link:
https://www.fiammalabs.io/
Logo (High resolution, will be shown with rounded borders):
https://s3.fiammalabs.io/FiaBtc512X512.png
Current TVL:
0
Treasury Addresses (if the protocol has treasury)
Chain:
Ethereum, Aptos, Sei, Core, Arbitrum, Base, ZKSyncEra, Polygon, BSC, Unichain, Plume
Coingecko ID (so your TVL can appear on Coingecko, leave empty if not listed): (https://api.coingecko.com/api/v3/coins/list)
Coinmarketcap ID (so your TVL can appear on Coinmarketcap, leave empty if not listed): (https://api.coinmarketcap.com/data-api/v3/map/all?listing_status=active,inactive,untracked&start=1&limit=10000)
Short Description (to be shown on DefiLlama):
Fiamma BTC is a 1:1 pegged wrapped BTC, which is minted by a trust-minimized BTC bridge Powered by BitVM2 protocol. It enables universal cross‑chain interoperability, allowing native Bitcoin liquidity to be safely unlocked and utilized across multiple blockchain ecosystems. By verifying zero‑knowledge proofs on Bitcoin via the BitVM2 protocol to minimize trust assumptions, Fiamma BTC provides a secure and scalable pathway for integrating Bitcoin into DeFi applications.
Token address and ticker if any:
Ethereum: 0x22F0E0a4c97ff43546dad16d43Ef854C773F0e08
Aptos: 0x75de592a7e62e6224d13763c392190fda8635ebb79c798a5e9dd0840102f3f93
Sei: 0x60C230c38aF6d86b0277a98a1CAeAA345a7B061F
Core: 0x60C230c38aF6d86b0277a98a1CAeAA345a7B061F
Arbitrum: 0x60C230c38aF6d86b0277a98a1CAeAA345a7B061F
Base: 0x60C230c38aF6d86b0277a98a1CAeAA345a7B061F
ZKSyncEra: 0x60C230c38aF6d86b0277a98a1CAeAA345a7B061F
Polygon: 0x60C230c38aF6d86b0277a98a1CAeAA345a7B061F
BSC: 0xafB253A80CEb3d1a5eeF3994C0d1C92c2f027524
Unichain: 0x60C230c38aF6d86b0277a98a1CAeAA345a7B061F
Plume: 0x60C230c38aF6d86b0277a98a1CAeAA345a7B061F
Category (full list at https://defillama.com/categories) *Please choose only one:
Bridge
Oracle Provider(s): Specify the oracle(s) used (e.g., Chainlink, Band, API3, TWAP, etc.):
Implementation Details: Briefly describe how the oracle is integrated into your project:
Documentation/Proof: Provide links to documentation or any other resources that verify the oracle's usage:
forkedFrom (Does your project originate from another project):
methodology (what is being counted as tvl, how is tvl being calculated):
Fiamma BTC TVL represents the total amount of Bitcoin bridged across all chains through the Fiamma Bridge, a trust‑minimized bridge built on the BitVM2 protocol.
Github org/user (Optional, if your code is open source, we can track activity):
https://github.com/fiamma-chain