pull down to refresh
100 sats \ 0 replies \ @Filiprogrammer 9 Oct \ parent \ on: Wallet of Satoshi is available in the US but balances & transactions are public lightning
The old custodial mode is not affected.
Is the project more or less dead, and totally overshadowed by Lightning?
It was never really alive in the first place.
In particular, I would be curious to know what are its relative merits/demerits against lightning, in terms of transaction convenience, fungibility of Sats, anonymity, privacy and trust model?
| Liquid | Lightning |
|---|---|
| You have to trust the federation members to not rug you. | Trustless |
| Fees scale with transaction size in bytes (better for larger payments) | Fees scale with payment amount (great for tiny payments) |
| Payment amounts are private but addresses still traceable | No public ledger, receiver does not know who the sender is |
Some on-chain software wallets matching these requirements:
- Sparrow wallet
- Electrum
- Blockstream Green (technically contains JavaScript but does not use Node.js/npm)
Only a little ETH it seems:
https://etherscan.io/address/0xfc4a4858bafef54d1b1d7697bfb5c52f4c166976
You still need the data to validate the block. During initial block download a node still needs to download the OP_RETURN data from somewhere. But it is true that OP_RETURN does not touch the UTXO set.
A block mined on the current consensus might not get accepted by nodes with the new OP_RETURN limit, thus causing a chain split. All miners would have to also implement that limit.
Very odd: https://ocean.xyz/stats/bc1qrp5dx0pnlh3yxnlw8mj4tw6dm9emlwdgncvtc6
One miner apparently contributed 30% of the entire network hashrate for a few hours and didn't find a single block. This has to be fake or block withholding but why would they do that??
As already stated in #1090261, if it's just about getting your LND node up and running again, you can just use neutrino as the chain backend by starting LND with
--bitcoin.node=neutrino --feeurl=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json.When it comes to getting your Bitcoin node up and running again, then as I already said in #1088425 since it seems your blockchain got corrupted, (presumably due to a flaky RAM connection) you will have to re-download the chain.
Seems like your block 251415 is corrupted and possibly others aswell. This might be some leftover file system corruption from before. Did you run a file system check (fsck)? Even if that does not return any errors, some of the bitcoin block files have gotten corrupted. The safest way to completly get rid of the corruption would be to reformat the drive and redownload the blockchain. (as annoying as that sounds)
Also when formatting the drive, make sure to use a journaling file system or ZFS. This helps detect file system corruption and also repair it in some cases.
Huh, that's interesting. Let's hope it really was just some dust, corrosion or improper seating. Good to hear that it works now! Hope it stays that way, I wish you luck!
i ran a few memtests and it seems to fail at anything over 4gb
A failing memtest is a strong indication that something is wrong with your memory. At least one of your memory sticks seems to be faulty. If you have multiple RAM sticks in your system, you could try removing one and rerun the memtest and see if it passes. If it does pass, then the stick that you removed must have been the faulty one. You could then either proceed to run your system without the faulty RAM stick and just deal with the fact that you have less memory, or you could buy a new memory stick as a replacement.
Really cool in theory! But this might not be practicable. Everyone making a transaction would also have to publish a proof. And verifying a proof also comes with some computational cost, potentially opening up a DoS attack vector.
312 sats \ 1 reply \ @Filiprogrammer 30 Jul \ parent \ on: Bitcoin node suspected hardware/disk issue bitcoin
A year ago I cheaped out when buying this exact 2TB SSD. At the time of buying I unfortunatelly did not pay attention to the fact that it does not have DRAM cache. This causes it to slow down to a crawl during high write pressure.
Also it only took me a few months for the first I/O errors to start appearing with this SSD.
Next time you buy an SSD for a Bitcoin node you should make sure that it has DRAM cache. When it comes to SSD brands, Crucial and Samsung are usually good.
Coming back to your problem, you might want to run a SMART test on your SSD and see if it reports any errors. Also check your logs for any file system errors. It could theoretically also be a RAM issue. So might make sense to run a memtest.
This is built on Rust with (Bitcoin style) encryption, whole new architecture.
Bitcoin does not use encryption. It uses digital signatures.
L402 already exists. But of course Cloudflare has to invent its own Fiat version.
Still, Euro or not, I think everyone has been wrecked by inflation post-COVID.
Not sure what you mean. Everything has been getting cheaper in sats.