I was reading about Bluetooth Low Energy, which led to the idea of running Lightning nodes completely offline. From there, I began to wonder:

• Are there any existing proposals or positive discussions regarding the air-gapped Lightning Network?
• What technical challenges did people identify when making lightning work with BLE/Wi ‑ Fi mesh?
• Can someone point out that I study or contribute to papers and implementation experiments related to me?

PS: I’m not used to Lightning Network at all, so I might have overlooked aspects that contradict the idea of an air-gapped setup. If so, apologise!

Today, we (the Devcon organizing team) are excited to make public a new way to get involved in next year’s event, and one that should make Devcon an experience that better represents Ethereum as a whole.

Devcon Improvement Proposals (DIPs) are a new tool to involve collaborative community input from across the ecosystem. They are aimed at improving the Devcon experience by formalizing a process to get your ideas heard and integrated into the event.

Why now?

In previous posts, we’ve touched on doing more to represent the entire Ethereum ecosystem at Devcon. However, doing so at any one event has become more and more challenging over the years. In many ways, this is a welcome problem to have, since the challenge is thanks to the growth in both size and diversity among builders, presenters, attendees, organizations and everyone else that’s participating.

While there was a time when everyone involved might have easily fit into a classroom, we’ve long since passed a point where demand exceeded supply in more ways than one (e.g. the amount of tickets, talk slots, or dogfooded applications).

So while we took first steps in solving for specific areas of past difficulty in our launch post earlier this year, we’ve also tried to be proactive when thinking about how to factor for things that no one team might think to include on their own. And that’s led us here.

How do DIPs work?

Let’s dig in. The best way to get started with DIPs is by visiting the DIP github repo and by joining the conversation over at the new Devcon Forum.

As a first step, we recommend posting your idea in the Devcon Forum to receive feedback from a wider community. Once things feel a bit more defined, you can submit a formal proposal. From the time of a submission, you’ll be able to receive feedback from our team and others to help refine ideas, to discuss how they might fit into the program, and more.

The process is inspired by the PEP, BIP and EIP processes, and while this new experiment is a bit more centralized (in that the approval of proposals ultimately lies with the Devcon team), we are excited to have a new way to branch out and hope to find consensus on a whole bunch of newly proposed ideas. The goals of DIPs are for everyone to feel heard, to have a more open discussion, and (most importantly) to improve the event by listening to and learning from the innovators around us.

What might DIPs look like?

If this process sounds rather abstract to you so far and you’re wondering what DIPs might actually look like, you’re in luck! DIPs are just being made public today, but the Devcon team has been working with a few teams to trial-run the first proposals in recent weeks.

Some of our first proposals include trying to make Devcon carbon neutral, enabling hotel and flight bookings through a FOSS decentralized travel marketplace, preparing a permissionless treasure hunt, and providing attendees with a smart wallet card during the conference.

Wrapping up

We know that the Ethereum ecosystem has simply grown too large for our team alone to be aware of every great idea out there. With the aid of DIPs, combined with your awesome continued involvement, we can make Devcon more representative of our community than ever before.

For more information, everyone is welcome to check out DIP-0, to take a look at the DIPs already submitted, and to join the forum to participate in new and ongoing discussions. We can’t wait to hear from you!

The US Securities and Exchange Commission (SEC) has opened public comments for two proposed cryptocurrency exchange-traded funds, or ETFs, from asset manager Franklin Templeton to be listed on the Chicago Board Options BZX Exchange.

In separate filings on Tuesday, the SEC said it was instituting proceedings that could allow the US exchange to list and trade shares of the Franklin XRP ETF and Franklin Solana ETF. The Cboe BZX Exchange filed for a proposed rule change with the SEC in March to allow for approval of the investment vehicle, which the regulator delayed in April, pushing its deadline for a decision until Tuesday.

“Institution of proceedings does not indicate that the Commission has reached any conclusions with respect to any of the issues involved,” said the SEC in both filings. “Rather, the Commission seeks and encourages interested persons to provide comments on the proposed rule change.”

Upon publication in the federal register, the SEC notices will effectively push the deadline to decide on whether to approve or disapprove of the Franklin Templeton ETFs by 35 days, to July. Though the US regulator has already greenlit spot investment vehicles for Bitcoin (BTC) and Ether (ETH), many companies are vying to be the first to be approved for tokens like XRP, Solana (SOL), and others. 

Related: BlackRock drives $412M Bitcoin ETF inflows amid Israel-Iran conflict

A new day at the SEC under Chair Atkins?

US exchanges with proposed listings from several asset managers have already filed with the SEC for listing and trading investment vehicles with exposure to SOL or XRP, including Bitwise, ProShares, and 21Shares. The SEC has radically altered its regulatory approach to digital assets under the Trump administration and the president’s pick to chair the agency, Paul Atkins, by dropping several high-profile enforcement actions against cryptocurrency companies.

It’s unclear whether this handling of digital assets could extend to ETFs tied to XRP or Solana. However, Trump proposed having both assets as part of his plans for a US crypto stockpile.

Magazine: Arthur Hayes doesn’t care when his Bitcoin predictions are totally wrong

]]> https://earlybirdsinvest.com/sec-opens-franklin-templeton-xrp-sol-etf-proposals-to-comments/feed/ 0 42589 https://earlybirdsinvest.com/what-kind-of-contract-proposals-are-being-considered-for-bitcoin-in-2025/ https://earlybirdsinvest.com/what-kind-of-contract-proposals-are-being-considered-for-bitcoin-in-2025/#respond Sun, 23 Feb 2025 14:01:56 +0000 https://earlybirdsinvest.com/what-kind-of-contract-proposals-are-being-considered-for-bitcoin-in-2025/

February 19th What kind of contract proposals are being considered for Bitcoin in 2025?

Jeremy Rubin is urging the Bitcoin development community to build a consensus under the Bitcoin Judica research institute for contract proposals to improve trading, security and programming efficiency. Bitcoin is well known for its conservative development culture, but the application of contracts can open advanced financial applications, open safes, and improve expansion without decentralization. But the debate is still happening between supportive supporters and those worried about changing the basic design of Bitcoin.

Major contract proposals

This is a summary of the top covenant proposals being discussed.

1. ON_CHECKEMPLATEVERIFY (CTV)

• Summary: CTV allows transactions to help enhance transaction efficiency, congestion control and privacy without allowing prior spending terms and allowing any calculations.
• Applications: Vault, Payment Group, Congestion Control, Lightning Network Factory.
• Status: Suggested and discussed in BIP-119, but not fully consensus.

2. OP_CHECKSIGFROMSTACK (CSFS)

• Summary: With CSF, scripted Bitcoin validates signatures from any data and opens the same capabilities as smart contracts. This allows you to build more complex transaction structures while ensuring safety.
• Applications: Union System, Safe Vault, Discaler Log Agreement (DLC), and Multi Signature Security Security.
• Status: Consider CTV for the original contract upgrade.

3. OP_CAT and arithmetic and encryption activities

• Summary: OP_CAT (data connection) has been removed from Bitcoin, but is now considered to be reintroduced along with elliptical digital manipulation and curves. These additions will improve Bitcoin’s scripting capabilities.
• Application: Smart contracts are evidence of more flexible and advanced encryption and an improvement in multi-signature schemes.
• Status: Controversial due to concerns about complexity and potential security risks.

4. OP_VAULT

• Summary: OP_VAULT is designed to enhance Bitcoin security by imposing wait times before providing a recovery mechanism in the event of hacking or loss of locks.
• Applications: Advanced security management solutions, Bitcoin storage for organizations, and theft protection.
• Status: Positive developments with proposed BIP-345.

5. OP_TXHAS

• Summary: These suggestions extend CTV by allowing scripts to commit to the transactional part rather than the entire output. This gives you more flexibility while maintaining CTV decisions.
• Application: Smart contracts are more advanced and improve lightning networks and custom payment terms.
• Status: Still in the initial discussion and development stages.

6. anyprevout (apo)

• Summary: First designed to upgrade your Eltoo Lightning network, APO allows signed transactions without accurate input, allowing for flexible payment structures and updating non-interactive channels.
• Applications: Lightning Network (ELTOO), State Chain, Payment Team Upgrades.
• Status: Suggested on BIP-118 and is currently under evaluation.

7. OP_TAPLEAF_UPDATE_VERIFY (TLUV)

• Summary: In TLUV, the script TapRoot can change the internal tree structure, execute conditions for future use, and provide a more advanced version of Covenant Bitcoin.
• Application: Allows smart contracts against fraud and dynamic contract structures.
• Status: Discussed with pilots.

8. Catt (all contract)

• Summary: CATT is a comprehensive contract frame that integrates OP_TXHAS, OP_CAT, CSFS and arithmetic activities into an integrated system, allowing developers to enhance flexible smart contracts.
• Applications: Extend multipurpose trading forms, decentralized financial applications, and second-class solutions.
• Status: Still in the theoretical stage, the components are developed independently.

9. Matt (merkleize everything)

• Summary: Matt uses Merkle Trees to implement smart contracts against fraud, allowing complex programming conditions without relying on external authentication mechanisms.
• Applications: Safe Vault, JoinPools, Multi -Stage Financial Contracts.
• Status: In the first idea stage and test.

So which suggestions are most supported?

Currently, CTV and CSF are the two most widely discussed proposals and are the most supported. They are considered minimal improvements, but offer great benefits such as transactional and congestion control without increasing excessive complexity.

OP_Vault is attracting attention thanks to its ability to enhance the security of Bitcoin depositories by allowing for wait times. This is especially useful for long-term storage and organizations.

Issues and outlooks

Some proposals such as OP_CAT and CATT promise great potential, but they run into resistance due to concerns about complexity and security risks. Achieving consensus in the Bitcoin community is always a major challenge, but if successful, these upgrades will open up a more flexible and competitive way for Bitcoin to be in the digital finance space.

The end result depends on the ability to find commonalities between developers and the broader Bitcoin community.
Don’t forget to follow the bitfinex Vietnam Community telegram, Twitter & Facebook To update articles, information and events as soon as possible!

]]> https://earlybirdsinvest.com/what-kind-of-contract-proposals-are-being-considered-for-bitcoin-in-2025/feed/ 0 21379 https://earlybirdsinvest.com/what-contract-proposals-are-being-considered-for-bitcoin-in-2025/ https://earlybirdsinvest.com/what-contract-proposals-are-being-considered-for-bitcoin-in-2025/#respond Sat, 15 Feb 2025 06:55:14 +0000 https://earlybirdsinvest.com/what-contract-proposals-are-being-considered-for-bitcoin-in-2025/

February 14th What contract proposals are being considered for Bitcoin in 2025?

The appeal by Jeremy Rubin of Bitcoin’s research and development organization Judica to build a consensus on contract proposals that can improve transaction efficiency, security and programmerism is bold. Bitcoin has an infamous, conservative development culture, and upgrade proposals are being scrutinized due to concerns about security risks and unintended consequences. If adopted, contracts could allow for improved financial applications, safes and scalability while maintaining decentralization. However, the broader debate reflects the gap between those who advocate for careful innovation and those who are cautious about changing the basic design of Bitcoin. It remains uncertain whether Rubin’s initiative will lead to widespread agreements, but it rekindled debates over the evolution of Bitcoin.

What does Jeremy Rubin’s recent call for action mean for the consensus on the contract?

Jeremy Rubin appeals to the Bitcoin development community to build a consensus on contract proposals, highlighting the need for structured, coordinated efforts to introduce meaningful upgrades to Bitcoin’s scripting capabilities. I did. A contract is a limitation on how you can spend your Bitcoin expenses, allowing for advanced features such as payment pools, vaults, and crowd control. Rubin’s approach supports a stepwise implementation starting with OP_CHECKTEMPLATEVERIFY (CTV) and OP_CHECKSIGFROMSTACK (CSFS), followed by OP_CAT and additional encryption and arithmetic operations. These upgrades are designed to improve Bitcoin’s programmership while maintaining security and decentralization. However, Rubin acknowledges the difficulty of reaching a consensus on protocol changes, as previous upgrade attempts have shown that the Bitcoin community is extremely cautious when changing base layers. It’s there.

The challenge of achieving consensus on Bitcoin comes from its decentralized nature and its strong preference among developers for stability over rapid innovation. Unlike other blockchain ecosystems that frequently introduce new features, the development process for Bitcoin is intentionally slow and conservative. Reluctance to adopt change without overwhelming agreement reflects concerns about potential security risks, unintended consequences, and difficulties in reversed changes in implemented protocols. Bitcoin upgrades require that new features not introduce systematic vulnerabilities or change the core network principles before activating careful review, peer review, and rigorous testing. There is.

The introduction of contracts to Bitcoin, if adopted, could significantly expand the functionality of the network without compromising the security model. Features such as CTV and CSFS allow for more efficient transaction batching, improved privacy mechanisms, and enhanced scalability solutions such as ARK and Lightning Network Channel factories. The second phase, which incorporates OP_CAT and cryptographic operations, further enhances Bitcoin’s scripting capabilities, allowing for more sophisticated smart contract functionality, while still taking other blockchain ecosystems into Web3, where smart contracts are located. Complete avoids the risks associated with the programming language that are found in something. He was exploited by bad actors many times. Advocates argue that these changes will make Bitcoin more competitive in financial applications without introducing unnecessary complexity.

Ultimately, Rubin’s proposal highlights the tension between innovation and conservatism in Bitcoin development. Some developers have advocated carefully introducing new features to expand Bitcoin use cases, but are skeptical of changes that could result in centralized risks or unintended consequences. I’m a developer. The process of generating consensus around contract upgrades requires thorough discussion, technical verification, and community-wide support. If successful, these upgrades could pave the way for more efficient transaction mechanisms, strengthening financial applications, and increasing flexibility in Bitcoin scripts, allowing networks to withstand censorship and to meet future needs. You will be able to adapt. However, the outcome of this effort will depend on whether developers and the wider Bitcoin community can find a common foundation on the path forward.

Overview of various contract proposals in Bitcoin

The following agreements are major changes proposed to Bitcoin’s scripting system, allowing users to enforce terms on how they can use future coins. These proposals introduce new opcodes to enhance the programmability of Bitcoin while maintaining the security model. According to the website Covenants.info, the following is a summary of the major contract proposals:

1. ON_CHECKEMPLATEVERIFY (CTV)

• overview: With CTV, transactions specify given spending terms and allow for more efficient transaction batching, congestion control, and enhanced privacy mechanisms. It ensures that the output must follow a specific expenditure template without allowing any calculations.
• Use Case: Vault, payment pool, congestion control, lightning network channel factory.
• situation: It was proposed in BIP-119 and is widely discussed, but has achieved a full consensus.

2. OP_CHECKSIGFROMSTACK (CSFS)

• overview: With CSFS, Bitcoin scripts validate signatures from any data, allowing smart contract-like functionality. This makes it easier to build complex transaction structures while maintaining security.
• Use Case: Enhanced security mechanisms for federation systems, secure vault, careful logging contracts (DLC), and multi-signature wallets.
• situation: Upgrading your initial contract will be considered in conjunction with CTV.

3. OP_CAT and arithmetic and cryptographic operations

• overview: OP_CAT (concatenation) was previously removed from Bitcoin, but is now being reconsidered for reintroduction, along with arithmetic and elliptic curve manipulation. These additions will improve Bitcoin’s scripting capabilities and allow for more efficient execution of smart contract functions.
• Use Case: More flexible contracts, highly encrypted proofs, and improved multi-signature schemes.
• situation: It is controversial due to concerns about potential complexity and security risks.

4. OP_VAULT

• overview: OP_VAULT is specially designed to improve Bitcoin custody security. It provides a safety net against theft by introducing a mechanism to implement delays before transferring funds, allowing users to collect funds during delay periods.
• Use Case: High-security self-reliance solutions, institutional Bitcoin storage, and protection against hacked or compromised keys.
• situation: It is actively developed with the proposed BIP-345.

5. ON_TXHASH and ON_CHACKENXHASHVELYIFE

• overview: These suggestions extend CTV by allowing scripts to commit to part of the transaction rather than to the entire output set. This gives you more flexibility while maintaining some of the deterministic behavior of CTV.
• Use Case: More advanced smart contracts, improved Lightning network functionality, customizable payment terms.
• situation: In early discussion and development.

6. anyprevout (apo)

• overview: Originally designed for Eltoo Lightning Network upgrades, APOs can sign transactions without specifying exact inputs, enable flexible payment structures, and enable updates to non-interacting channels.
• Use Case: Lightning Network Upgrade (ELTOO), Status, and Payment Pool.
• situation: It has been proposed in BIP-118 and is currently receiving further evaluation.

7. OP_TAPLEAF_UPDATE_VERIFY (TLUV)

• overview: With TLUV, TapRoot scripts can modify the internal tree structure, enforce conditions for future use, and provide more advanced versions of Bitcoin Coben agents.
• Use Case: Enabling fraud prevention smart contracts and dynamic contract structures.
• situation: Experimental and under discussion.

8. Catt (all contract)

• overview: Catt is a comprehensive contract framework that integrates OP_TXHASH, on_cat, CSFS, and Operations on a unified arithmetic operational system allow developers to build highly flexible smart contracts.
• Use Case: Generic transaction templates, distributed finance applications, and scalable second-tier solutions.
• situation: It is still in the theoretical stage, with various components being developed independently.

9. Matt (merkleize everything)

• overview: Matt uses Merkle Trees to implement fraud prevention smart contracts, enabling complex programmable conditions without relying on external verification mechanisms.
• Use Case: Secure safes, JoinPools, and Multi Stage Financial Contracts.
• situation: In the early conceptual and testing stages.

Which proposals are the most popular in the Bitcoin community right now?

Of the current contract proposals, OP_CHECKTEMPLATEVERIFY (CTV) and OP_CHECKSIGFROMSTACK (CSFS) are the most widely discussed and have gained considerable traction. These proposals are considered minimally impactful improvements and allow for features like transaction batches, congestion control and more sophisticated smart contracts. In particular, CTV is considered one of the most uncontroversial suggestions, as it has received extensive reviews and does not allow arbitrary calculations. Developers advocating this upgrade claim that it can be implemented with minimal risk and great benefits for scaling and security.

Another contract proposal that will attract attention is OP_Vault. It focuses on enhancing Bitcoin security by enabling a time-locked recovery mechanism for lost or stolen funds. The proposal has gained strong support from people concerned about the risk of self-identification, as it allows users to create safes that can only withdraw funds after delays, and time to intervene with owners in the event of unauthorized access. I’m giving it. OP_VAULT has been particularly accepted by those seeking to improve Bitcoin’s ease of use for long-term savings and institutional custody, as it provides a built-in safety net against certain types of attacks. However, although the concept has been widely appreciated, this challenge remains to achieve consensus on how it is implemented and activated.

More ambitious proposals like OP_CAT and CATT (contract everything) have sparked debate, but have faced more resistance due to concerns over security, complexity and potential unintended consequences. Masu. OP_CAT, which enables data concatenation in Bitcoin scripts, allows for stronger smart contracts, but also raises concerns about increased minor extractable value (MEV) risk and the possibility of script-based centralization I will. Some developers have proposed a step-by-step approach starting with CTV and CSFS and introducing OP_CAT along with arithmetic and elliptic curve manipulation, but there is still some hesitation within the wider Bitcoin development community. Overall, CTV and CSF appear to have the strongest support for short-term activation, but OP_VAULT and OP_CAT continue to generate interest, with discussions on their feasibility and potential trade-offs. It’s there.

]]> https://earlybirdsinvest.com/what-contract-proposals-are-being-considered-for-bitcoin-in-2025/feed/ 0 19586