Once someone knows a particular wallet address is yours, they may follow on-chain records to find your holdings, transaction times, and which DeFi protocols you’ve used.
If you frequently borrow and lend or trade, the subsequent flow of funds may also be continuously tracked.
▧ <a>Starknet</a>’s strkBTC gives BTC holders another option:
By bridging BTC from your own Bitcoin wallet to Starknet, you can deposit strkBTC into lending markets, use it for collateralization, or provide liquidity—seeking returns according to the rules of the specific application. When you need to reduce information exposure, you can also switch the selected balance to Shield status via Xverse or Ready X.
Both public usage and shielding balances are based on strkBTC, so you don’t need to switch to another wrapped asset.
After entering Shield status, other people who view on-chain records can’t directly see the selected balance or the protected transfer details. However, this doesn’t mean all DeFi operations are automatically hidden.
At the moment, when you deposit strkBTC into Vesu as collateral, the common process is still to go back to the public state first. Which protocols you can directly access in shield mode depends on the wallet and the features supported by the product at that time.
Privacy also has boundaries: compliance checks are in place for entry and exit, and viewing keys are held by an independent third-party auditing firm. Related activities may, under certain circumstances, be verified within a limited scope.
Bridging currently relies on a federation mechanism. Solutions like BitVM, OP_CAT, and others that reduce reliance on federations are still on the roadmap.
🛑 strkBTC does not guarantee returns, and it does not turn BTC into an anonymous asset.
It’s suitable for those who are willing to take on bridge and smart-contract risks, want to use BTC on Starknet, and don’t want all balances and transfers by default to be shown to the outside world.
If you frequently borrow and lend or trade, the subsequent flow of funds may also be continuously tracked.
▧ <a>Starknet</a>’s strkBTC gives BTC holders another option:
By bridging BTC from your own Bitcoin wallet to Starknet, you can deposit strkBTC into lending markets, use it for collateralization, or provide liquidity—seeking returns according to the rules of the specific application. When you need to reduce information exposure, you can also switch the selected balance to Shield status via Xverse or Ready X.
Both public usage and shielding balances are based on strkBTC, so you don’t need to switch to another wrapped asset.
After entering Shield status, other people who view on-chain records can’t directly see the selected balance or the protected transfer details. However, this doesn’t mean all DeFi operations are automatically hidden.
At the moment, when you deposit strkBTC into Vesu as collateral, the common process is still to go back to the public state first. Which protocols you can directly access in shield mode depends on the wallet and the features supported by the product at that time.
Privacy also has boundaries: compliance checks are in place for entry and exit, and viewing keys are held by an independent third-party auditing firm. Related activities may, under certain circumstances, be verified within a limited scope.
Bridging currently relies on a federation mechanism. Solutions like BitVM, OP_CAT, and others that reduce reliance on federations are still on the roadmap.
🛑 strkBTC does not guarantee returns, and it does not turn BTC into an anonymous asset.
It’s suitable for those who are willing to take on bridge and smart-contract risks, want to use BTC on Starknet, and don’t want all balances and transfers by default to be shown to the outside world.