Largest Bitcoin In The Sky price

squidfra #2 - bitcoin ---------- one of the major unlocks by @ikadotxyz is that a smart contract on @SuiNetwork can control native bitcoin with speed, scalability, decentralization and zero-trust security. this is huge, and literally not possible anywhere else. however, ika is low level infrastructure, and although the cryptography behind generating a bitcoin signature in a fast, scalable, decentralized and zero-trust way is the most difficult challenge from a research perspective, there are many other challenges for devs who want to utilize bitcoin on their application. for example, how does a smart contract on sui "know" what the state of bitcoin is? how can the signed transactions be submitted to bitcoin? how are bitcoin transactions constructed on sui? how to use dwallets to optimize and reduce bitcoin gas fees and latency? what if i want a synthetic bitcoin to work out of the box with an existing protocol? and in the future how can native bitcoin protocols on defi be seamlessly interoperable? it makes sense to build squidfra tackling these challenges and others, so devs can just focus on their use case. of course many other pieces of squidfra can be useful for bitcoin use cases, but bitcoin's rudimentary design, its significance and the market demand for bitcoin solutions - warrant an entire category of squidfra solutions focused solely on bitcoin. ---------- 1. problem it solves for most people, bitcoin is crypto. as @RobertZarembaIT likes to say, it completely dominates the crypto mindshare. bringing access control and programmability to bitcoin is one of crypto's holy grails and there are many many teams trying to do that. very few are actually doing it with native bitcoin (most are issuing derivatives), and those who do - have many issues (as i'll detail in section 3). whether it's a light client (or full node...) that can be used to verify against the bitcoin state, a smart contract that can construct / deconstruct bitcoin transactions and run them against policies, a relayer system to broadcast signed transactions to bitcoin, an out-of-the-box bitcoin synthetic or an interoperable standard for controlling native bitcoin - having robust bitcoin squidfra on sui means that anyone who wants to build bitcoin into their use case has the best optionality to plug into different solutions and minimal heavy lifting to do themselves. ---------- 2. use cases it enables the genericity and flexibility of ika basically makes any use case possible on bitcoin, but let's highlight some of the categories where the right squidfra can give sui devs unfair advantages over other players in the space: i. custody: enabling decentralized custody with zero-trust security for the first time is a game changer. it solves one of the biggest problems for adoption and being able to have robust bitcoin custody access control policies implemented on-chain without reducing security (like @Aeon_HQ and @COVAULTxyz are doing for example) are a huge competitive advantage that sui builders will have when tackling the bitcoin custody space. ii. native bitcoin defi: enforcing any logic directly on native bitcoin, where the user holds the user share, can be used to design new interoperable defi protocols that utilize native bitcoin for swaps or as collateral - without removing user ownership. a new design is required because it will rely on p2p transactions held in escrow by the protocol (future transactions), instead of the popular pool model. iii. synthetic: bitcoin synthetics are the easiest way to work out-of-the-box with existing protocols without designing new mechanics. although they can't offer the full zero-trust advantage as protocols working with native bitcoin directly can, any bitcoin synthetic created on sui using ika (like nbtc for example) will be instantly more decentralized than any existing derivative. ---------- 3. existing alternatives most bitcoin solutions are based on derivatives - so receiving a native btc deposit to a bitcoin address that is fully controlled by a completely centralized multisig or a fairly centralized and permissioned mpc network - and minting a wrapped token in exchange. this is true for practically every "xbtc" token - wbtc, cbbtc, tbtc, sbtc, lbtc (where it goes through babylon, but same story) etc. this also applies to places where the multisig / mpc network is used to control native bitcoin directly without minting a derivative, because it has the exact same trust assumptions (user gives full control of bitcoin to a handful of trusted 3rd parties) platforms that try to do things directly on bitcoin without taking custody away from the user are cool but scarce and very limited. they're limited because they're forced to use bitcoin script (like @lava_xyz) or exploit very specific cryptographic hacks (like @babylonlabs_io) and therefore can offer extremely limited and specific functionality, and scarce because they have a super complex and inefficient system, struggle with performance, and sometimes also include hidden risks. ---------- 4. competitive advantage with ika ika unlocks speed, scalability, decentralization and zero-trust security in a way that is not possible anywhere else. but most of all, robust bitcoin squidfra can unlock unprecedented optionality, flexibility and simplicity for devs. whether a sui dev focusing on a bitcoin use case wants to prioritize security, performance, abstracted user experience or competitive value - they can pick and choose their model and have it all work out of the box. ---------- superstar team @goNativeCC are leading the charge right now with creating bitcoin squidfra, they've already built the first spv (simple payment verification - a bitcoin "light client") in move on sui, implemented a testnet version of their synthetic bitcoin nbtc, and recently also won @kostascrypto's impossible challenge building the basis for a bitcoin full node on sui. and while native are definitely establishing themselves as the bitcoin squidfra leaders, i expect a few more teams to operate in this space which is huge in terms of potential and can definitely support multiple teams. ---------- tomorrow it's finally time to get into "accountfi" squidfra - allowing devs to fully leverage the unique zero-trust account transferability capabilities of dwallets