Share this page!

Jeff Garzik Profile picture
Twitter logo
21 Dec, 3 tweets, 2 min read
Important details to emphasize, in re #LedgerHack #blockchain #cryptocurrency #cryptocurrencynews

This also illustrates why #privacy is important when shopping.
Zero cost ways to improve your privacy:
- Use a separate email address for shopping
- New one every year; "burn" the old
- Use a Google Voice number, rather than your own
- Ditto; rotate GV numbers yearly.
- Rotate CC numbers yearly.
- Use gift & crypto debit cards
Low cost ways to improve your privacy:
- Rent a UPS Store or Post Office box, and receive mail and packages there.

Other basic privacy tips, worthwhile to review: usa.kaspersky.com/blog/privacy-t…

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with Jeff Garzik

Jeff Garzik Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jgarzik

Jeff Garzik Profile picture
18 Dec
1/ Excited - Soon to be opening the doors to the @VesperFi beta launch #DeFi #cryptocurrency #permissionless #ethereum #blockchain #PaymentFreedom #SaveTheDate medium.com/vesperfinance/…
2/ Beta testers will be able to test our first product - ETH, WBTC and USDC "Holding Pools"

Holding Pools are yield aggregating vaults, similar to other projects, with a focus on longevity, and a professional, simple, clean experience.

This is a familiar DeFi primitive.
3/ Holding Pools at Vesper are scored with liquidity quality scores internally, resulting in a "conservative" or "aggressive" summary label. Conservative yield sources, such as @compoundfinance, @AaveAave and @MakerDAO are "seasoned", with time-in-market, real-money tested.
Read 10 tweets
Jeff Garzik Profile picture
8 Oct
1/ Yesterday: My L1 chain has better, faster tech than #Bitcoin or #Ethereum. It is not compatible with existing software or tooling, but will nevertheless overcome network effect and momentum to become the next Ethereum. Invest in my Ethereum killer.
2/ Today: My L2 rollup chain has better, faster tech than #Bitcoin or #Ethereum. It is not compatible with existing software or tooling, but will nevertheless overcome network effect and momentum to become... Invest in my...
3/ Investors routinely underestimate the value of iterative evolution - trial-and-error over time - sunk into software, tooling, auditing software libraries & the 1,000 other elements of a software ecosystem.

Smart competitors build on top of that, rather than starting from zero
Read 5 tweets
Jeff Garzik Profile picture
6 Oct
1/ Supportive of this innovation and effort, and encourage people to participate.
2/ #Ethereum bot ecosystems often unintentionally evolve to single-bot-wins situations, where it is pointless & costly to run a bot that consistently comes in "2nd place"
3/ Bot 1 consistently wins liquidation auctions. It becomes unprofitable for others to play the game, resulting in a single player game. If the player (Bot 1) leaves or malfunctions, no other bots step up and take its place, due to incentives & deteriorated ecosystem.
Read 4 tweets
Jeff Garzik Profile picture
21 Feb 19
Finally spent some time studying #Ethereum Merkle Patricia Tree github.com/ethereum/wiki/…
1. It is an elegant data structure for Eth, creating a cryptographically stable merkle root, no matter the data insertion order.
2. Oh boy, it really punishes your hard drive storage.
In my past life at Red Hat, I wrote the ATA (aka IDE) drivers for Linux, so I know a bit about data storage and hard drives.
Here is why Eth is so punishing on data storage, and why SSDs/NVMe are a field requirement for Eth:
Like Bitcoin, Eth has poor cache locality:
* Huge db, which means each Next Page is less likely to be in page/disk cache.
* Keys are hashes, which means each Next Query Key is uniformly random, and therefore equally unlikely to be “close” to any recent past query.
Read 6 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

Like this author's thread?

Get emails when @jgarzik has new unrolls!

Check out other threads from @jgarzik!

Read all threads by @jgarzik