Gracious Interests

6.2K posts

Gracious Interests banner
Gracious Interests

Gracious Interests

@GraciousIntere1

We talk #Crypto Crypto and blockchain education Linktree: https://t.co/dIUMP85dQx… Support us: https://t.co/yi6EPowB0h

Присоединился Ekim 2020
1 Подписки165 Подписчики
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
Kind reminder. Adam Back is pro-spam because he earns a living with it. I'll repeat that again in plain English: - @adam3us , a Bitcoin "legend" who created hashcash (which is anti-email spam), earns his living by allowing people to spam the Bitcoin network. Verified here:
Dimitri-H 🇧🇪@Dimi_h

People are wondering why Bitcoin legend @adam3us is pro-spam and maintaining the stance that Core V30 is harmless. The answer is quite obvious. As CEO of blockstream, and heavily tied with Liquid Network, he earns part of his income with people minting spam. Illustrated:

English
5
19
83
2K
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
Been reading a bit through these proposals made by @defenwycke . Stumbled upon it in the dev. mailing list. It is a workable proposal on policy level. Basically it defines carried data in a transaction and allows more precise filtering on policy level. Interesting read.
Defenwycke@defenwycke

BUDS + segOP Explained People keep stuffing all sorts of extra data into Bitcoin transactions — metadata, L2 anchors, inscriptions, random blobs, whatever. Bitcoin lets this happen, but it doesn’t really understand any of it. To the node, most of these bytes look the same. So I’ve drafted two proposals and have tested code that basically tries to clean this situation up a bit, without changing what Bitcoin is or taking anything away from anyone. *BUDS* BUDS is just a way to describe data. Nothing more. It doesn’t change consensus, doesn’t restrict inscriptions, doesn’t “ban” anything. It’s basically a common vocabulary so that tools, nodes, explorers, miners, wallets — anyone — can talk about transaction data in a consistent way. It gives things names. It sorts data into rough tiers. It can tell you what kind of data dominates a transaction. That’s it. No rules, no enforcement. Just clarity. *segOP* Segregated OP_RETURN does touch consensus, but in the smallest way possible. It adds a proper, structured lane for non-payment data so it doesn’t get shoved into witness or script in weird ways. Think of it as giving that data a clean room rather than letting it spill into every corner of the house. It uses TLV (type-length-value), it has a commitment in an OP_RETURN output, and it’s priced normally — no more hiding large blobs in discounted witness space. Old nodes still verify the blocks fine. Wallets that don’t care about segOP don’t need to do anything. It’s opt-in. How They Fit Together BUDS describes what the data is and segOP provides where the data goes. They’re separate. They don’t depend on each other. But together they make Bitcoin’s data landscape far easier to reason about — for everyone. Why This Matters This isn’t about changing Bitcoin’s purpose. It’s about cleaning up the reality that transaction data today is messy and scattered. If we can describe data better (BUDS) and house it more cleanly (segOP), then a few things become much easier: Nodes can prune data cleanly, so long-term storage becomes more predictable. Mempool behaviour gets more consistent because you’re not guessing what a random blob is. Explorers, wallets, miners, and indexers can make decisions using actual structure instead of fragile heuristics. Core devs have a clearer path to tighten old limits later on without accidentally breaking legitimate use cases. And again: nothing here blocks inscriptions, ordinals, L2s, or any other use case. All of that still works. The difference is simply that Bitcoin can understand what it’s looking at, instead of parsing noise. Links BUDS github.com/defenwycke/bip… segOP github.com/defenwycke/bip…

English
1
3
5
183
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
To be fair, @nvk has a point. The Cat is a retroactive technical solution which goes against Bitcoin philosophy. Which, despite my comments made, I am not a full-on backer of the proposal. My focus remains on BIP 110 (formerly BIP444) to prevent new spam to occur. It would be nice to see the spam/scam getting their due for their greed...but I do not find it weighs up to breaking ideals and morals which made Bitcoin as it is. The spam is a scar. It is part of Bitcoin history sadly enough.
English
1
2
7
185
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
Does, in Bitcoin / Crypto , greed & fear indicator of "extreme greed" always translate to bullish market? ----------- While there might be a correlation, it is not exclusive. “Extreme Greed” CAN occur during a bearish market. The “Greed&Fear” indicator is more of an indicator to market sentiment. I.e. it translates the overall market “demand” and is very susceptible to context. “Extreme greed” can both refer to people being “greedy” for Bitcoin (i.e. high demand for $BTC) or people being “greedy” for profit (i.e. cashing out). Context is important. During bearish cycles can “extreme greed” occur as well. This can happen with Crypto who crossover into a lower trading bound unexpectedly whereby the majority of the market sees opportunity to buy-in at extremely low prizes. This will result in a sudden price-surge as available liquidity dries up due to sudden high demand. The indicator can show a sudden lapse from “Extreme Fear” to “Extreme Greed” on very short notice. It is for this reason that the “Greed&Fear” indicator isn’t used as a serious ratio when doing technical analysis. Other factors play-in as well. “Greed&Fear” only indicate at what the current sentiment is but says nothing of importance on a fundamental or technical level.
English
0
2
2
386
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
@RealKeithWeiner So all the - Bitcoin futures - Bitcoin ETF's - Exchanges - Strategic reserves - bussinesses Are not a sign of adoption? Granted that I am not a fan of most of them, it still is a clear signal that TradFi is adopting it.
English
0
1
4
213
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
A look into the mind of a typical shitcoiner. "I don't believe in all those NFT's.... but I might regret making money scamming people". That's why The Cat and BIP-110 are needes. Moral integrity to Bitcoin as hardest digital money ever.
nico@nicoxbt_

yes i think ordinals are spam/scam but i also think this might me a great chance to buy the next alien/ape cryptopunk for a couple sats few years from now i will probably regret not buying any bc i think its stupid lol

English
2
9
28
760
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
Honest nodes establish policy and relay information based on their established policy rules. They don't exclude others. The data relayed has a certainty to be accepted, validated and verified by the entire network. Dishonest nodes force themselves into a closed relaying system. The data they relay will only be accepted through force by "a tolerant minority" which does the validation and verification.
Majorian / BIP-110@MajorianBTC

The Node Wars are revealing threat vectors we did not consider closely enough until recently. Namely, that honest nodes could go to war with one another. Peer banning could be a race to the bottom.

English
0
2
5
101
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
The spam which started in 2023, and continues to this date plague the Bitcoin network, is already causing problems in regards to upcycling of (CPU) hardware to built cheap and effective nodes. Some of my old DIY Bitcoin nodes are seeing frequent outages due to intensive CPU usage as soon as synchronization occurs with the network. Always near the same block range (those mined in 2023). Frequent restarts after cool-down are needed (3-4 restarts to date in the last 3 days of syncing). Currently "updating" these to Bitcoin Knots V28.1.knots20250305. Opted to download the entire chain from 0 to monitor the effects of spam on synchronization with "older" refurbished and dedicated hardware. This is a hidden and undershined argument in regards to network growth and security (and negative effect of spam on Bitcoin node running). Things need to be lightweight and low-tech to see more mainstream adoption. It is problematic to see a 10 year old CPU that can run most modern browser and mobile games get overheated and shutdown in trying to sync with a simple monetary network... almost struggling to get up to date.
English
7
9
44
9.3K
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
An undershined effect in the Bitcoin (client) node wars is the effect of spam on upcycling hardware. The spam effect makes syncing harder for "older" hardware which hinders adoption in low-tech environments. A deterrent for Bitcoin as global decentralized currency x.com/Dimi_h/status/…
English
3
2
7
106
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
Miners follow policy as established by nodes. The BIP 444 to push filters at consensus level is to kick out all the preferential peering by "tolerant minorities" (as backed by Core-apologists) and let Bitcoin function as intended: as a currency.
Steve Barbour@SGBarbour

This BIP explicitly hopes miners will adopt and enforce it for moral reasons, but failing that it relies on the State to force miners to adopt it. It is the Karen BIP.

English
0
2
3
163
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
@LukeDashjr 's BIP444 breakdown - as well as offering rebuttals -------------- What does BIP444 do? -- -- -- -- As the title of the BIP444 mentions = Reduced Data Temporary Softfork. It is a temporary softfork aiming to limit the size of data fields at the consensus level. Basically the opposite as what Core V30 introduced when they removed the limits on the OP_RETURN function. The difference here is that BIP444 will be re-introducing the limits (temporarily) for OP_RETURN as well as limit the possibility to store data in other functions. Those other functions being mainly related to exploits that Ordinals abuse since early 2023. The introduced limits will effectively halt the creation of Ordinals. What limits does BIP444 introduce? -- -- -- -- This is taken directly from the BIP444 proposal: - New output scriptPubKeys exceeding 34 bytes are invalid, unless the first opcode is OP_RETURN, in which case up to 83 bytes are valid. - OP_PUSHDATA* with payloads larger than 256 bytes are invalid, except for the redeemScript push in BIP16 scriptSigs. - Spending undefined witness (or Tapleaf) versions (ie, not Witness v0/BIP 141 nor Taproot/BIP 341) is invalid. - Witness stacks with a Taproot annex are invalid. - Taproot control blocks larger than 257 bytes (a merkle tree with 128 script leaves) are invalid. - Tapscripts including OP_SUCCESS* opcodes anywhere (even unexecuted) are invalid. - Tapscripts executing the OP_IF or OP_NOTIF instruction (regardless of result) are invalid. --> When reading through the proposed limits, we immediately notice that the limits are directly imposed on functions barely used and whose current established limits were either too high or unused. Noticeable is that the imposed limits on actively used functions are in line with genuine monetary use and the prevention of pushing data. We even see a push for OP_RETURN use (which Core V30 proponents pushed to mitigate abuse) while setting the limit again to 83Bytes. In the follow-up tweet, I'll be debunking and giving nuance to some made counter-arguments. BIP444 proposal link: github.com/dathonohm/bips…
English
2
4
18
2.4K
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
If confirmed real, it may be correctly assumed a significant portion of Core "domination" is compromised. Even worse, it implies Bitcoin is less decentralized than thought. As a pleb, it is that mich more important to start running your own Bitcoin node. Privately at home.
Snapolino@snapolino

W000t on the AWS outage in us-east 5k core nodes did go down... lol but not Knots nodes... We will win because Nodes connect to different C-nets and we have true Cnet majority with Knots! Worrysome that so extremely many nodes run on some one elses PC/Server !!!!

English
0
4
8
254
Gracious Interests ретвитнул
Dimitri-H 🇧🇪
Dimitri-H 🇧🇪@Dimi_h·
In Bitcoin, we are used to say "blockchain technology". The whitepaper mentions it as "timestamp server". The term blockchain is a result of simplification of the technical description. It's accurate.. but not precise.
mononaut@mononautical

If you ask a bitcoiner what a blockchain is, it’s remarkable how few people will mention the defining trait of blockchains - that each block header commits to the hash of the previous one. That’s what makes the chain immutable.

English
0
2
1
110