Let's talk about $ESD and $DSD coupons.

$DSD coupons is something to behold with two waves of expirations: epoch 721-749 and 756-767.

Up to epoch 767 there are 78m coupons to expire which represent 53m DSD with a 45% premium.

There are also 4m more coupons after epoch 767.
$ESD looks much worse as there still are only 8.4m coupons to expire negligibly reducing the supply.

However, there is also EIP-16 in the works which will make coupon principals unburnable.

This will make ESD coupons more attractive, theoretically reducing the supply greatly.
Technically, EIP-16 could be implemented in DSD as well but I really doubt that DSD holders will vote it in as it's in their best interest to let the coupons burn decreasing the supply.
I think we will see those DSD coupons expiring because even if the whales will try to pump the price to trigger expansion, DSD holders will meet them at $1 dumping the price back to $0.8.

But it's up to the whales as it's impossible to detect how much dry powder they have left.
UPD: wrong ESD chart, here's the correct one.

• • •

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

Keep Current with Alex Moskovski

Alex Moskovski 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 @mskvsk

27 Aug 19
Ethereum Syncing Diary [GETH edition] - Day 1

Today I'm going to try and sync a full Ethereum node like @ercwl did but using geth instead of parity.

The playground is an 8 CPU / 32 GB DO droplet ($160/mo) + 500 GB volume ($50/mo)

So, let's geth --syncmode="full" --cache=28672
This is to be a full non-archive node, which means it's going to be executing all transactions of every block starting from the genesis.

When it finishes syncing (I believe we will be done within 3 weeks) I'm going to scale the droplet down a bit to make it less expensive.
Geth has spread itself across all available CPU quite nicely. Memory usage is hovering around 3.3 GB.

The blockchain has eaten up a little more than 1 GB of the SSD at the moment.

Syncing early Ethereum history makes me a bit nostalgic.
Read 13 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!