VCs entered an order of magnitude below your average entry
you don't wanna start bagholding their bags just cuz you feel like its time to rotate out of your current thing
they hedge their holdings ahead of unlocks, resulting in downwards pressure long before unlock dates
1
27
bitmeme retweeted
Replying to @kelvinfichter @banteg
Because I trust secp256k1, but I don't trust the EVM Β―\_(γ)_/Β―
bitmeme retweeted
regardless if people like it or not, the matter of the fact is that taproot *did* make it just easy enough to productize the blobspace in bitcoin with a single input such that people are going to start doing it to a material extent.
the 1 sat/vB reign is over, "fun" is coming back to bitcoin.
the historically low demand for bitcoin block space as a result of BTC no longer being the primary way to transfer value between exchanges will prove to be a historical anomaly as we see its demand replaced by people building meta-protocols ontop.
ordinals and inscriptions is one such use case, sovereign rollups is another. but the buck doesn't stop there.
there's an entire EVM and zk landscape that would be more than happy to act as a buyer of last resort on bitcoin if bitcoin's blobspace is both 1) more reliable and 2) cheaper than ethereum's. the market for both these blockspaces will harmonize.
this also means that MEV is coming to bitcoin in a serious way.
maybe this fucks up the chain, maybe it doesn't. if it does, it's not any particular person's fault.
on the negative side, it means that the bitcoin ecosystem may have to adapt MEV mitigation strategies, mining pools in particular. hashrate quickly centralizes around the most MEV-savvy pool if nothing is done since they offer higher rewards per hash in an industry that lives and dies on the margin.
on the positive side, it may mean that we can put "bitcoin is going to require inflation to survive after the block subsidies are gone" behind us, which many loud critics argue is the largest problem for bitcoin.
also, if MEV is already becoming a problem via meta-protocols, then there will no longer be game theoretical arguments to avoid BIP300/301, drivechains, actual zkrollup softforks and other things aside from their own idiosyncratic and implementation-specific risks. there will likely be less resistance in supporting those softforks, as they won't introduce MEV, the MEV will already be there.
the battlefield of bitcoin has changed, and this is a direct result of segwit+taproot.
the faster you realize this and adapt to this new reality, the easier you'll have facing its challenges, and the more you will prosper from its opportunities.
good luck, folks.
bitmeme retweeted
Evaluate any Bitcoin transaction privacy with a few lines of code.
Boltzmann is available for Python and Java (Android too).
github.com/Samourai-Wallet/bβ¦
github.com/Samourai-Wallet/bβ¦
bitmeme retweeted
Huh, @Medium is now in the censorship business. Suspended an account for posting a guide to using Bitcoin anonymously.
A blog is literally the easiest content type to find/build alternatives for, what the fuck are you guys doing??
coincache.net/2019/01/02/bitβ¦
bitmeme retweeted
This was going to happen eventually. All regulated stablecoins (Paxos, USDC and Gemini dollar) are obligated to know the source of funds coming to redemption. ccn.com/paxos-standard-hasslβ¦
bitmeme retweeted
βWhy Bitcoin Matters for Freedomβ - the Human Rights Foundation in TIME time.com/5486673/bitcoin-venβ¦ read the whole thing. I could barely decide what to highlight
bitmeme retweeted
Required reading if you still think that miners control bitcoin. @kyletorpey and @AaronvanW are two of Bitcoin's most valuable historians/chroniclers. Vital work.
forbes.com/sites/ktorpey/201β¦
bitmeme retweeted
Reminder: Bitcoin transactions are never *from* an address, only *to* them. Despite popular misinformation websites pretending there are, there is in fact NO sender identification in the Bitcoin protocol, and UTXOs are NOT associated with addresses.
(This is technical info.)
bitmeme retweeted
Pro-tip: read the @rustlang standard library source code! It's surprisingly simple, demystifies the language, and you can find all kinds of neat ideas like how slice support uses a union under the hood for conversion to/from explicit fat pointers: github.com/rust-lang/rust/blβ¦
bitmeme retweeted
The BCH split is entertaining because it brings the BCH faction's hypocrisies to bear.
"forking is governance!" β enjoy your fork
"only hash power matters" β so you'll support SV if it wins then?
"big blocks at all costs" β so you'll support SV (128 mb) over ABC (32 mb)?
bitmeme retweeted
If you have recently received a very small amount of BTC in your wallet unexpectedly, you may be the target of a "dusting attack" designed to deanonymise you by linking your inputs together - Samourai users can mark this utxo as "Do Not Spend" to nip the attack in the bud.





![TDevD [No KYC, no T&C, no π] (@SamouraiDev) profile picture](https://pbs.twimg.com/profile_images/1546385065877426178/7cMBaBnV_400x400.jpg)















