pull down to refresh
0 sats \ 1 reply \ @darwin 14 Nov \ parent \ on: Why Roger Ver Deserves A Presidential Pardon conspiracy
He put his reputation on line for Karpeles, pretty bad move, IMO:
https://www.youtube.com/watch?v=UP1YsMlrfF0
His strong support for Bitcoin Cash (BCH) could be viewed as harmful to BTC. Essentially, during the blocksize wars, he stood on the wrong side.
But for me personally, he caused harm by recommending MtGox before its collapse. He did issue an apology, though: https://www.youtube.com/watch?v=GRIJ_jpmwzo
On balance, I personally believe he has done more good than harm over the years. Especially in the early years, he was very influential, hence the nickname “Bitcoin Jesus”.
This is definitely not because of him selling BTC for BCH. He got into this shit by renouncing his U.S. citizenship in 2014 and not properly doing his "exit taxes".
Bloody details here:
https://www.justice.gov/opa/media/1350116/dl?inline
You can always ask ChatGPT to condense any post to size of your liking. With a bit of training you can even teach AI the level of your current knowledge/expertise so it produces personalized outputs.
For example here is response asking ChatGPT4 to condense the post into three paragraphs:
The post discusses the challenges and potential of the Bitcoin Lightning Network, focusing on its evolution and current issues. Initially hailed as a decentralized payment network with cheap transactions and the ability to run personal nodes, the reality has shifted. Many users now rely on custodial wallets instead of self-custodial solutions like Mutiny Wallet, which aims to address these challenges.The author identifies two major issues with the Lightning Network: channel liquidity and the offline receive problem. Channel liquidity, unique to Lightning, confuses users due to its complexity and inconsistent fee structures, while the offline receive issue arises because users must be online to sign and claim payments. Attempts to solve these problems, like Zeus Pay lightning addresses, have led to more issues, like stuck payments. These challenges make self-custodial Lightning less popular, driving users towards easier, custodial solutions.Beyond these issues, the post delves into deeper problems like the impact of on-chain fees on channel liquidity and potential solutions like anchor channels and package relay. However, these solutions are not perfect and often require a compromise, like holding on-chain funds for fee bumps. The author suggests that large-scale lightning nodes might be a better focus, given that most users prefer custodial wallets for their simplicity and efficiency. The post concludes by exploring future directions, including the need for soft forks to implement covenants for scaling Bitcoin ownership and the potential of fedimints to dynamically share ownership over a group of UTXOs, offering a promising direction for Bitcoin scaling.
Trezor Suite has coin control feature. With that you should be able to craft transactions you desire.
If not already trezor user, you should be able to run Trezor software emulator with your Trezor Suite, this should allow you to intialise it with your existing seed:
Please note that this is quite unsafe setup. I would recommend running this on a clean offline computer against your own (synced) bitcoin backend. Then after signing a transaction, instead of broadcasting it, copy raw transaction (under details) into a file to a usb drive. This way you prepare all transactions you need. You can broadcast those transaction later from any online computer running bitcoin core or via services like https://mempool.space/tx/push
No mention of https://tropicsquare.com?
GENESIS