for rarteds like us
Jolla (Sailfish OS), Volla (Volla OS / Ubuntu Touch), Pixel (GrapheneOS)... a lot to consider.
Not true. Opening and closing addresses are not the same.
Example: https://mempool.space/lightning/channel/987720982097362945
Sure.
So here's my small setup running bitcoind, pool_sv2 and translator_sv2.
Starting up translator_sv2 (both self-compiled and binary from github) with given translator-config.toml, I get errors about missing fields: "supported_extensions" and "required_extension". Even if empty, both need to be present in the toml file, they are commented out. pool-config.toml has it right and loads correct.
$ ./translator/translator_sv2 -c config/translator-config.toml
Translator proxy config error: Bad `config` TOML deserialize: `missing field `supported_extensions``
After uncommenting both options, pool_sv2 and translator_sv2 are starting up just fine. 👍
Yesterday we launched a full stack @StratumV2 web deployer for developers who want to spin up Pool and miner side apps locally.
https://stratumprotocol.org/developers
Would love feedback from devs and anyone comfortable with CLI. Anything unclear? What sucks, what can be better? https://blossom.primal.net/9aeb347f387b461a7bbf816a99ea5f5f8dbc9a01a915f973c028f411eee9bf65.mov
Pretty awesome! It has been a small riddle to find out how everything connects to each other. This makes it a lot easier.
https://minibolt.minibolt.info (x86/AMD64)
https://raspibolt.org (ARM)
Don't trust, verify. If you ever wanted to compile bitcoin core binaries for yourself, here's a quick guide. Adjust build parameter for your needs (this one builds for headless version (no GUI)):
No way! You are Dirk Bach 😄
Haha you are right. It works. CI updated to backfill 365 days of commits.
Approach NACK
might be resolved "temporary"
no auto-softforks? 😅
... time to start DCA again
Discovery of the Day: Classic meets Bitcoin
A Bitcoin song by a German opera tenor
https://www.youtube.com/watch?v=C-eMyOXk9Mg
nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycs558km nostr:nprofile1qqsqx84rqcvglmnrr2r0rg8ynnhg70tzty4ju7l9lr430z8ryldngzs6qc3pm
#artstr #musicstr #music #art
Awesome! Is there a setup guide to follow out there?
It's 100kb
> datacarriersize is increased to 100,000 which effectively uncaps the limit (as the maximum transaction size limit will be hit first).
Within these 100kb there may be multiple op_returns.
https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes-32406.md
we did some zap tests on this note… we made six attempts to⚡zap this note, at 0x09e8587cb55205b7@ln.bitcoin-21.org, over a period of 6 minutes. Six of the zaps were successfully paid... please check for 6 satoshis received. problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (the zap spec requires that the zap receipts be sent to the relays specified in the zap.) this means a nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.
Thank you. Yes, it's setup in a wild way. I'll fix this soon.
It's done. Sub-sat/vB fee settings merged into Bitcoin Core v30.0 to be released in October.
https://github.com/bitcoin/bitcoin/pull/33106
In case you cannot wait. Add to bitcoin.conf:
minrelaytxfee=0.00000100
incrementalrelayfee=0.00000100
But mind that not alot software out there that already support sub-sat fees. nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqguwaehxw309ahx7um5wgkhyetvv9ujuamvweejuumsv93k2qpqhea99yd4xt5tjx8jmjvpfz2g5v7nurdqw7ydwst0ww6vw520prnq70qrf6 has it in Sparrow Wallet's master branch, probably expected in next release version. Also not alot of bitcoin node will relay sub-sat fee transactions right now or right from the start of v30. For now you might need some luck to get them through to miners.
According to my bitcoin node:
19,900,000 coins have now been mined into circulation
$ bitcoin-cli gettxoutsetinfo
> "total_amount": 19900016.44574898