SBF Profile picture
Oct 23 19 tweets 4 min read
1) Whelp, that was an interesting few days.

A retrospective.
2) NOT LEGAL, REGULATORY, OR FINANCIAL ADVICE

THOUGH MAYBE A LITTLE BIT OF SPECTACLE ADVICE AT THE END

Also: note that most of the below is about the *US* policy landscape. Other countries may differ.
3) First off—a huge thanks to everyone who gave constructive feedback, comments, and criticism—notably @ErikVoorhees and @RyanSAdams but too many more to name. I’ve revised my post some already, and will continue to do so.
4) Thanks particularly to everyone who highlighted the core of crypto: economic freedom.

The freedom to own your own assets;
to own your own data;
to build your own programs
5) None of this works if you need active permission to do everything: commerce grinds to a halt.

If you show up at 7-11 to buy a bagel, and next thing you know you’re pulling out a passport and social security number and taking selfies, something’s gone wrong.
6) On the DCCPA: a bunch of the comments the DeFi community is making are extremely important.

Here’s where it stands:
7) The core goal of the bill is to regulate *centralized* crypto venues.

The main *DeFi* touchpoint is: *how can a regulated centralized entity interface with DeFi?*
8) In particular, it is *not* making claims about what DeFi devs, smart contracts, and validators must do. It’s looking to eventually establish guidelines about how e.g. FTX’s platform--or Fidelity's--could interface with DeFi contracts.
9) This gets right what the infrastructure bill a while ago got wrong: that devs and validators aren’t platforms, and shouldn’t be regulated as such. Which is a huge step forward!

But again we’ll have to see the final language; I’d only support a version that gets this right.
10) The most surprising thing is how constructive and receptive the lawmakers are to everyone's feedback--including the DeFi community; it’s one of the reasons I’m optimistic about the bill.

Granted, we’ll have to see the final language.
11) One thing that may ultimately be required centralized entities like FTX: there are likely to be disclosure/etc. requirements, and potentially “customer suitability tests” of some sort.

It’s really important that this is done in an equitable way.
12) Historically, these have been a toxic combination of wealth tests and variants on ‘do you have a fax machine’ that are highly exclusionary towards the poor, minorities, and rural investors.

It’s bad to gate building wealth on having wealth.
13) Instead, they should drive at the core question:

Does the customer fully understand the product and its risks? Are they making an informed decision?

If you’re going to gate products on regulated exchanges, do it on understanding, not wealth.
14) (You can check out ftx.us/derivs for an example of what this could look like)
15) (Also I thought the section on hacking was interesting and going to be one of the more controversial ones. Boy was I wrong about that.

But either way I think the 5-5 standard would help give people a lot more confidence and comfort! And save people a lot of money.)
16)On sanctions:

a) validators and smart contracts need to be free, permissionless, and decentralized
b) we should have tooling to make screening easier and quicker
c) I have sympathy for innocent people caught in broader blocks—that’s a policy conversation worth having
17) Anyway: I totally understand that lots of people will disagree with me on various points. That’s great—it means I have people to learn from.

And I really do think that regulation is going to get better, clearer, and create pathways for crypto to come back onshore.
18)While I don’t myself wear glasses, I’m excited to join our bespectacled brethren. It’s a huge honor to see the passion and intensity with which Bitboy regards me.

Maybe someday I’ll feel as strongly about something as he does about me.

19) Anyway, enough policy for now.

Back to building.

• • •

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

Keep Current with SBF

SBF 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 @SBF_FTX

Oct 23
1) Phishing sucks
2) NOT FINANCIAL ADVICE
3) Usually, phishing looks like an email, and it has a bad attachment, or something.

In crypto, the scams have gotten sophisticated.

For instance--we have a team of people who work to make sure fake FTX clones don't gain prominence.
Read 16 tweets
Oct 23
1) Binance converts USDC --> BUSD, and we see the change in supplies.

Thus begins the Second Great Stablecoin War. (The first one, fought in ~2018, ended with USDC and USDT edging out TUSD/GUSD/USDP.)
2) What's different this time is:

a) positive interest rates --> more revenue for stablecoins

b) by now they've all learned the core lesson: NEVER EVER BLOCK REDEMPTIONS or your stablecoin will no longer be stable
3) At this point, we're probably the largest unaligned players in the stablecoin ecosystem. Bybit, the various blockchains, tradfi, and market makers are as well.

(Worth asking what the futures are of USDK, HUSD, etc.)
Read 4 tweets
Oct 19
1) As promised:

My current thoughts on crypto regulation.

ftxpolicy.com/posts/possible…
2) At a high level:

a) we need regulatory oversight and customer protection

b) we need to ensure an open, free economy, where peer to peer transfers, code, validators, etc. are presumptively free

c) we should establish regulation--and until then standards--to ensure (a/b)
3) First, it means that we have blocklists and not allowlists for illicit financial activity.

We need fast, reliable lists of addresses associated with illicit finance.

But peer to peer transfers should generally be free as long as they're not going to sanctioned actors.
Read 15 tweets
Oct 12
1) When it comes to oracles,

you just have to make up your own damn mind
2) NOT FINANCIAL ADVICE, NOT LEGAL ADVICE
3) Let's say that you have a margin trading protocol which allows cross-margin between a bunch of different assets.

Your algorithm is "require 30% initial margin and 20% maintenance margin"--i.e. allow ~3x leverage, and margin call accounts if they get up to 5x leverage.
Read 23 tweets
Oct 10
1) Equitable direct access:

the way market access should work

ftx.com/settings/api
2) On your API page, you can now whitelist an IP address to get direct, fast access to FTX's servers, bypassing Cloudflare.

This should take API order latency down significantly.

ftx.com/settings/api
3) Traditional examples of this cost millions of dollars and are reserved for privileged firms.

Even on crypto exchanges, it's usually reserved just for VIPs.

But that's dumb: there's no reason to just make the fastest firms faster.

Everyone should have equitable access.
Read 5 tweets
Oct 10
1) This Thanksgiving:

FTX, Evolved.
2) Over the next month, we'll be rolling out a bunch of improvements to FTX's matching engine.

In fact we've already started.
3) We'll be rolling out a whole new order matcher, lower latency API pathways, and a whole slew of other features.

These have been in the works for most of the year.

They're almost ready to release.
Read 7 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

Don't want to be a Premium member but still want to support us?

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(