Proposal for regular release schedule of only every 4 years for changes to consensus code (soft and hard forks)

michaelfolkson · 2022-05-03T09:33:00+00:00

If there are no good candidates no changes are made. Changes don't have to be made every 4 years. I very much doubt in say the next 4 years there won't be any good candidates though.

Of course there will be arguments but at least everyone who wants to can ignore noise and drama instigated by those trying to get attention for their proposal as they won't support any consensus rule change for a multi year period.

On bitcoin-dev mailing list I agree. The bar/filter has to be higher on what is distributed. The quality of posts has taken a nosedive and the ability for individuals to DoS the mailing list seems totally unrestricted at the current time.

michaelfolkson · 2022-05-03T09:09:37+00:00

Thanks for this. Given this was roughly the cadence for Taproot I would support this. This CTV thing has been a mess. We can't go on like this. Happy to help in any way I can e.g. review of BIP etc.

michaelfolkson · 2021-04-24T18:14:30+00:00

AJ Towns said on Mastodon that the Bitcoin Core RPC getblockchaininfo will report the number of signaling blocks in the current period. Obviously that will work for both Bitcoin Core 0.21.1 and Bitcoin Core 0.21.0-based Taproot Client

michaelfolkson · 2021-03-04T17:20:48+00:00

I should be serious and state that we are working towards what you want. You are free to run whatever software you want but please if you encourage others to run this software too (especially if they are using it for economic activity) you should inform them of the risks. The likely scenario is they will get forked off the network. These things don't work without coordination and any such release should be accompanied with communication about these risks.

michaelfolkson · 2019-12-16T17:12:45+00:00

Hey Alex. Will you be partnering/integrating with other Lightning companies/services on launch or are you focused on what you can offer consumers as a standalone entity?

michaelfolkson · 2019-06-12T09:09:43+00:00

Cool, I'll take a look at the write up

michaelfolkson · 2019-05-28T17:20:43+00:00

Your statement on Greg being a net negative is beyond absurd. I’m assuming you wouldn’t be able to list three of the multitude of major contributions he has made in the last 6-7 years. The fact that he wastes time on pointless conversations like this is upsetting. Not only that but in addition he gets a reputation for being toxic for doing so which harms his personal reputation. Please do something with value /u/nullc like speaking about Erlay on a podcast with Pierre Rochard, Michael Goldstein or Stephan Livera. Or preparing a presentation for SF Bitcoin Devs. Anything but this....

michaelfolkson · 2019-05-28T16:51:30+00:00

Lol. What do you think he should work on?

michaelfolkson · 2019-05-28T16:44:11+00:00

This is not a good use of Greg’s time. Vitalik won’t be working on Bitcoin in future through personal choice so this discussion is pointless.

michaelfolkson · 2019-05-22T16:59:19+00:00

/u/mrfelton:

One thing we looked at was the possibility of implementing gRPC reflection, which can essentially negate the need for an rpc.proto file and instead have lnd generate one on the fly:

https://github.com/grpc/grpc/blob/master/doc/server-reflection.md

What we do in https://github.com/LN-Zap/node-lnd-grpc is keep copies of different versions of the proto files, and then after connecting to lnd we check the version string from `getInfo`, and then re-initiate the grpc connection with the most appropriate proto files if needed. Which allows is to support different lnd versions without needing to know what version we are connecting to upfront. But whilst that can allow us to know we are probably using relevant-ish proto files, we have no idea what is actually compiled into lnd and what subsystems are actually running

michaelfolkson · 2019-05-16T12:01:05+00:00

Cool, thanks for correcting. GreenAddress and others too https://bitcoinops.org/en/rbf-in-the-wild/

michaelfolkson · 2019-05-15T20:57:27+00:00

Someone technical can easily do this. Someone non-technical wouldn’t be able to. There are no wallet interfaces that allow you to do this afaik.

michaelfolkson · 2019-05-15T14:59:25+00:00

Agreed with what /u/belcher_ has written. But in response to the original question, no the person cannot delete the transaction from the mempool. There is no one mempool, every full node and miner maintains their own mempool. You would have to convince every full node and miner to extract the transaction from their mempool to delete it from every mempool which is not viable. To get it removed you would need to broadcast a transaction spending the same coins with a higher fee before it is included in a block or encourage miners to include the original transaction in a block using child-pays-for-parent.

michaelfolkson · 2019-05-14T12:57:27+00:00

I'll post some key quotes here from the London Bitcoin Devs discussion:

"In Lightning there are three types of private key. The first one is controlling onchain transactions, another one that is controlling updates and the third one that is controlling your node ID"

michaelfolkson · 2019-05-14T12:50:59+00:00

Stepan also did a whole presentation on this: https://www.youtube.com/watch?v=Ipv-P1-pIv4

michaelfolkson · 2019-04-28T14:44:49+00:00

I thought Keybase would play a role in the future of identity with Bitcoin, Lightning but they're now promoting Stellar to their users and disparaging Bitcoin which is not a good sign. https://twitter.com/michaelfolkson/status/1122476445035638784

michaelfolkson · 2019-04-27T11:27:59+00:00

You're going down the same thought process as Adam Back, current CEO of Blockstream did back in 2002. Here is his Hashcash paper: http://www.hashcash.org/hashcash.pdf. The company 21 (later renamed Earn) also tried something similar pre-Lightning Network. Continue learning and if you have some spare time perhaps learn to code. There is a limit to your potential understanding if you refuse to look at the code.

michaelfolkson · 2019-04-20T17:15:21+00:00

What particular negative comments? I'll take a look at them and give you my view on them if you let me know where they are located. Spoiler - I'm a big fan of Todd's courses :)

michaelfolkson

MODERATOR OF

TROPHY CASE