Avatar
Byzantine
5d1d83de3ee5edde157071d5091a6d03ead8cce1d46bc585a9642abdd0db5aa0
even the byzantine empire fell

this morning twitter broke all third party clients and my favorite twitterrific is dead. thank you damus and @jb55

everyone focused on the SBF ponzi is missing the slow train wreck: the pension system is on the verge of collapse.

I just left a late night meeting for a pension system on the west coast and things are very very bad.

this historic article gives context. and things are 10 times worse since this was written

https://www.forbes.com/sites/johnmauldin/2019/05/20/the-coming-pension-crisis-is-so-big-that-its-a-problem-for-everyone/?sh=1f96469e37fc

cpi calculation change https://www.financialexpress.com/investing-abroad/featured-stories/us-cpi-calculation-to-change-for-january-inflation-data/2944976/

U.S. CPI calculation change in January. CPI was formerly based on two years of consumption data. Now, CPI will be based on a single year of data.

ugggg...oh the irony.

oh really? where?

open a bar and call it XPUB

few realize the insane level of vulnerability there is in underwater cables https://www.lawfareblog.com/protecting-undersea-cable-system

holy hell, these guys roast good honey processed coffee https://literoasters.com

๐Ÿ“ฃ Revert and disable I2P "notransit=true" option of i2pd.conf to not relay any public I2P traffic! ๐Ÿšจ

Notice to node MiniBolt runners: It turns out that the I2P devs have opened an [issue](https://github.com/bitcoin/bitcoin/issues/26754) on the Bitcoin Core GitHub repo commenting that because they gave the option to enable the `notransit=true` parameter in the [official documentation](https://github.com/bitcoin/bitcoin/commit/71abee86dba8f311775104c518644c55c3e123cf):

\[...\] If you prefer not to relay any public I2P traffic and only allow I2P traffic from programs connecting through the SAM proxy, e.g. Bitcoin Core, you can set the no transit option to true \[...\] are having a heavy load on the I2P network since last December 19. Also comment that it is advisable to share as much bandwidth and transit tunnels as we can, to increase anonymity with coverage traffic, by contributing more to the I2p network than we consume. So they ask that we deactivate that option that you use activated. With all this, he already updated the "Privacy" section by removing that setting.

The steps to delete this configuration once we have already configured it, are the following:

With the "admin" user, stop i2pd:

$ sudo systemctl stop i2pd

Comment line 93 with "#" at the beginning of it (notransit = true), save and exit

$ sudo nano /var/lib/i2pd/i2pd.conf --line numbers

Start i2pd again

$ sudo systemctl start i2pd

And that's it, you could take a look at Bitcoin Core to see that it has detected i2pd running again after the reboot with:

$ tail --lines 500 -f /home/bitcoin/.bitcoin/debug.log

If for whatever reason you don't see that I2P is up in Bitcoin Core after the restart, `$ sudo systemctl restart bitcoind` and look again at the logs of the same

More info in the rollback commit: [https://github.com/twofaktor/minibolt/commit/99cae67a5150bb5b7deae3674cc958eb31c74a75](https://github.com/twofaktor/minibolt/commit/99cae67a5150bb5b7deae3674cc958eb31c74a75)

most journalism is not searching for truth but instead searching for balance

altruism is just selfishness with a generally accepted good outcome

nexo was just raided in bulgaria

https://www.reddit.com/r/minibolt/comments/109a9rc/new_signature_verification_process_for_bitcoin/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

๐Ÿ“ฃ New Signature Verification Process for Bitcoin Core ๐Ÿ”‘ โ€“ Based the on Guix attestation method to release new Bitcoin Core releases with Bitcoin Core developer's signatures

New method for signature check: [https://twofaktor.github.io/minibolt/guide/bitcoin/bitcoin-client.html#signature-check](https://twofaktor.github.io/minibolt/guide/bitcoin/bitcoin-client.html#signature-check)

GitHub repo of Bitcoin Core release attestations (Guix): [https://github.com/bitcoin-core/guix.sigs](https://github.com/bitcoin-core/guix.sigs)

?width=1628&format=png&auto=webp&v=enabled&s=f43106109194c3740212fcbd661e798b316a95b0

History:

PR that caused the broke and obsolescence of the old signature verification process: [https://github.com/bitcoin/bitcoin/pull/26598](https://github.com/bitcoin/bitcoin/pull/26598)

New GitHub folder of Bitcoin Core repo that stores the signatures:[https://github.com/bitcoin-core/guix.sigs/tree/main/builder-keys](https://github.com/bitcoin-core/guix.sigs/tree/main/builder-keys)

Thanks to [Gzuuus](https://twitter.com/gzuuus) for building the command which made magic possible ๐Ÿง™โ€โ™‚๏ธ๐Ÿงก

the climate emperors have no clothes https://archive.vn/r0NTb

one caveat is that you have to somehow communicate your relay to your followers. for example a relay bans joe or many relays ban joe. if you do not know the other relays that joe uses you will never see messages again.

nothing has intrinsic value