why not introduce policies to make it much less likely for inscriptions to succeed, or even a soft fork to redefine whats standard and valid here? so instead of asking whether OP_RETURN or Inscriptions, why not instead fight both and solve this issue more thoroughly? 🙂
I think an important distinction is: 1. filter based on transaction format 2. vs. filter based on transaction content format filters are trivial. content filters are difficult. imho filtering based on content or even intent requires centralizing complexity in filtering, while format based filters are trivial for everyone.
i think executive function is important as well, so they cant just solve problems, but plan how to achieve goals and execute and/or delegate imho.
i hadnt heard of arc before. it seems a counterparty is needed. if thats true, what does that counter party do and could it be replaced by a CRDT instead? ...sry if that doesnt make any sense. ...just trying to figure out what are pros/cons compared to lightning. if you have good links that give a good detailed summary, that wpuld help too 🙂
is it though? global public debt is definitely growing insanely fast, but global private debt grows faster. commercial banks who print the majorit of money are helping businesses worldwide to pay their employees - its all printed on the account of all the self employed businesses who do not have access to that money printing. this is real world capitalism as the world knows it since the industrial revolution or even since forever. blaming governmwnts isnt wrong, but its specificaly the money printers and those are not just government. blaming only the governmwnt is a one sided distorting story
absolutely 🙂
Absolutely. https://youtube.com/shorts/yIdr3jJ9juk?si=k6n67twjutAUJbl9 This needs to become an important discussion topic to educate more people in the bitcoin community who might not yet understand this. This will help us as a bitcoin community at large to resolve differences and avoid division
Interesting to learn, that **Bitcoin Core** is maintained by employees. The marketing bitcoin core was "decentralized" because it has so many contributors is a farce. There is no formal process, but instead a handful of existing maintainers pull in/up new contributors instead of the other way around. And of course, everyone is incentivized to stay on the payroll - ultimately who pays decides. https://www.youtube.com/live/3BFgoQawG7Q?t=8188s Thanks for shedding light on this. In fact - bitcoin developers can always ask for donations, but the point is - if you have a lot of bitcoin as a developer, you have stake in the game and helping to make bitcoin successful pays you. True decentralization means - if we already have employees implementing, then at least lets have them paid by a diverse set of companies and not all on the same group that keeps everyone on payroll. Thats really bad. I see knots vs. core as a huge improvement to decentralization and we should have even more implementations.
The gist of why knots and why BIP 444 to start making it a habit to always fight spam and fight it early, because publishing spam is a cost to spammers and to deny them their (scam) business model, mean they will sit on their costs instead of making profits from it. But if spam will cause net losses for spammers, they will not even try to spam in the first place and thus the bitcoin chain gets rid of spam, which is great. Let's all join this "whack a mole" game to proof to scammers trying to spam means making losses to stop them from even trying in the future. https://www.youtube.com/watch?v=5iUVWBr0a2U
That is why the pear stack matters (a.k.a hyper* stack) (a.k.a dat stack). https://docs.pears.com Its not compatible with nostr but rebuilding nostr as a concept on top of it will create nostr on steroids. More throughput with less issues. At some point we will have to do it 🙂 Those relay issues are solved, because for any particular peer, there is a way to discover all relays that have the data, so you dont have to follow specific relays. ypu can find them on demand.
That is why the pear stack matters (a.k.a hyper* stack) (a.k.a dat stack). Its not compatible with nostr but rebuilding nostr as a concwpt on top of it will create nostr on steroids. More through put with less issues. At some point we will have to do it 🙂
heard some feedback: > This is great and could be improved if supertestnet uses this config for the node: > feefilter=0 > blockreconstructionextratxnsize=300
Welcome to serapath spacestr profile!
About Me
(📍🇺🇸) nomadic 🍐⇄🍐 eco🌐 gamedev 🌈: https://playproject.io 🧙🏽: https://wizardamigos.com 🌱: https://datdot.org 🔮: https://dat-ecosystem.org 🏳️🌈☥: (they/them) 🦣 @[email protected] 🐦⬛https://x.com/serapath
Interests
- No interests listed.