Feed for tag: protocol
OP_DIFFICULTY To Enable Difficulty Hedges Without an Oracle and 3rd Party

Every financial market has bets, some are bets on the availability of a certain product, the price of a certain product at a certain point in time and on productivity and all markets depend on supply and demand, in metal markets the supply is the amount of metal that was produced this year, in Bitcoin that amount is fixed so people can’t bet on it. What you can bet on is how much it costs to mine Bitcoin at a certain time, specifically the difficulty, as the difficulty rises miners need more powerful, and probably more expensive, machines to be able to compete.

For anyone wanting to enter the mining business, this is the biggest risk there is, and while commodity markets offer futures and options to hedge risks, currently Bitcoin doesn’t employ this.

That’s why developer Tamas Blummer suggested the OP_DIFFICULTY, an opcode to enable hedges without any 3rd party interference, settled on the blockchain.

Accessing Bitcoin's ZeroMQ interface
In this tutorial, we will be taking a closer look at bitcoin’s ZeroMQ messaging interface. This interface is useful for developing applications which might require data related to block and transaction events from a Bitcoin core node.
Bitcoin wire protocol 101
Ever wonder how bitcoin nodes talk to each other? Well, in this tutorial we’ll be covering the raw details behind the TCP based bitcoin wire protocol, which could be considered lesser known than the more popular RPC interface.
lightning-dissector: A Wireshark Plugin for Lightning Network Protocol

Nayuta, a team currently developing a new Lightning Network implementation called ptarmigan, announced the release of a wireshark plugin for the Lightning Network (BOLT) protocol. The plugin is hosted here.

It’s alpha version, but it can decode some BOLT message. Currently, this software works for Nayuta’s implementation(ptarmigan) and Éclair. When ptarmigan is compiled with some option, it write out key information file. This Wireshark plug-in decode packet using that file. When you use Éclair, this software parse log file.

A BIP proposal for 'cancellable' transactions

Alejandro Ranchal Pedrosa and Tucci-Piergiovanni proposed a new BIP to extend OP_CSV1 and/or OP_CLTV2 to allow and interpret negative values.

The discussion that followed concluded that the BIP would be breaking a fundamental rule which is that valid transactions remain valid. This could lead to loss of funds when several transactions are made invalid.

Claiming an OP_RETURN prefix

OP_RETURN code has some interesting, but highly controversial, applications. It’s used to mark a transaction output as invalid, allowing users to burn bitcoin, its also used to add some data to a transaction or store data on the blockchain, which you shouldn’t do.

Some use OP_RETURN prefixes as a way of confirming that they are behind this transaction, using colored coins or storing data.

Recently there were discussions on how to claim these OP prefixes but some members of the community thought it was a bad idea as it would allow censorship and reduce anonymity.

This relates to an old BIP from 2016, but work on this BIP is still in progress.

Channel Rebalancing

Dmytro Piatkivskyi started the following discussion on lightning-dev regarding the topic of channel rebalancing.

There has been a lot of discussion on sending cycle transactions to oneself to ’re-balance’ the network. On LN mailing list [1] or numerous places elsewhere. There has been even a paper suggesting a smart mechanism to do the re-balancing (see Revive or Liquidity network [2]). My question is what do we actually get from it? [3] states that the distribution of funds in channels does not really affect the network liquidity. I can see cheaper fees or shorter paths if the network is kept balanced. But don’t you think that a smart fee strategy will do the job?

To save your time, [4] explains the gist from [3].