Replies (16)
Thnx for the post... this is sad, but I guess to be expected.
I think wicked is but he put a sad face on his picture so idk if he was actually lauging
Ah. Massive assholes
I genuinely want to understand this issue…are we saying bitcoin is harmed by fully used block space (like cpu cycles or RAM constraints?).
I don’t like spam. But with block size limit, does it really matter? And if it really does, then maybe block size needs to be smaller?
Luke argued for years that block size should be 300 kB. He’s rarely wrong, but I’m skeptical over this policy issue.
Need the physical location and name of PortlandHoDL ... asking for a friend. DM me.
Portland?
1) pretty much
2) no
3) congratulations on thinking this out.
I think on the first question some people are worried that too much arbitrary data (non financial txs) will make it cost peohibitive for people who want to use it as money.
Then smaller blocks probably wouldn’t help?
I guess the argument I’m making boils down to bitcoin is doomed, right? I mean, if it can’t work as intended when block space is fully used, either block space drops or bitcoin is not useful…feels like a strange conclusion but compsci isn’t always straight forward
i think he was the one who turned off mute to ask, if portland was at least running knots nodes.. sarcastically of course
Got it.
I imagine the truth most properly expressed woul look like a table comparing low resource full node performance with and without spam vs. Block height
Something like: rpi3 nodes will become impractical at blockheight xxxxxx with spam but will remain practical until xxxxxx+yyyyyy without spam or something like that.
Oh boo. He makes good videos