Curious & user obsessed fintech product maker. Tokenizing money. Innovation, Design, Security, Better markets, Stablecoins, Payments, Crypto, Cards
Maplewood, NJ
Joined July 2008
- Tweets7.1K
- Following1.5K
- Followers784
- Likes2K
Tom D retweeted
Anchorage Digital has submitted its application for swap dealer registration to support our continued growth as a leader in the options space, scaling past the $8B CFTC’s threshold for US based clients.
Anchorage Digital Swap Dealer, LLC has submitted its application to the National Futures Association (NFA) for swap dealer registration with the Commodity Futures Trading Commission (CFTC), aiming to offer institutions a regulated framework for trading digital asset derivatives, the same federal derivatives framework that governs the largest dealers in traditional markets.
Read why we registered and what it means for clients: anchorage.com/press-room/anc…
Tom D retweeted
A compromised laptop moved billions.
Our CEO & Co-Founder, @NathanMcCauley, on why a stolen device should never be enough to move client assets, and how Anchorage Digital was built so it isn’t.
Tom D retweeted
Digital assets don't matter until they reach the real economy. That is the whole job.
Join @Sergiofly's keynote as he discusses what it takes to get there, in Hong Kong on Nov 3, co-hosted with @RD_Technologies and @hashkeygroup.
RSVP: okt.to/aG4krF
The fact that the people coming out against tokenization of equities choose to wage war on the printed pages of the WSJ says everything you really need to know about how out of touch that side of the argument is.
There is a bit of an ad war around tokenization happening on the print pages (irony?) of the @WSJ. But it's a war that doesn't need to be fought.
The ads are arguing over tokenized security wrappers. For a host of reasons I've already written about, other than access, these aren't better alternatives to what's traded today. And the big exchanges are being forced to solve for access in the near term.
The way this happens is native issuance on chain. It's not mutually exclusive to (and is in fact fungible with) exchange issuance, and offers superior margin and lend capability. Like @Figure's OPEN. And these platforms work within the rules today.
This will be slow, then all at once.
Tom D retweeted
NYSE OWNER ICE TEAMS UP WITH TRADE[XYZ] TO BUILD A US MARKET FOR 24/7 PERPETUAL FUTURES ON HYPERLIQUID $HYPE, PENDING CFTC APPROVAL
Tom D retweeted
Ian is right; to avoid a dystopian financial surveillance system where both governments and corporations crush the average person, we need privacy.
Zcash is a start.
But we have to keep going, and we need to remember why we are building it.
10 years ago, we launched Zcash, making a private version of Bitcoin. But the origins go back to the 80s, when, in the wake of the Watergate scandal, cryptographers first dreamed of private electronic cash, and the story runs through Satoshi’s invention of Bitcoin.
Zerocoin came three years before Zcash launched in 2016. We’d written it as a zk-mix for Bitcoin, and then a year later, Zerocash, which introduced SNARKs to cryptocurrency and is now the de facto approach to private payments on chain.
More than 30 years before that, in the early 80s, cryptographers first dreamed of private electronic payments. This was right after the invention of public key cryptography, the Watergate scandal, the Church Committee’s revelations of intelligence agency wrongdoing, and an ongoing fight between the nascent academic crypto community and the government over regulations and alleged backdoors.
It was also right as it became clear that the growth of the internet and electronic payments would pose a major surveillance risk. Today, there are a number of cryptographers who think crypto is simply math, devoid of purpose, and a number of folks in cryptocurrency who do not care about privacy (or perhaps even cryptography). That was not the case in the 1980s.
Starting with David Chaum, cryptographers first designed e-cash, a centralized private payment scheme that required a trusted bank to blindly sign special tokens. These went nowhere: existing trusted institutions, like banks, didn’t adopt the protocols, and no one wanted to trust magic internet money run by a strange company. Then Satoshi invented Bitcoin, overcoming the trust issue by inventing a blockchain. Bitcoin’s key innovation was the blockchain, which replaced a trusted bank with a public database anyone could participate in running. Because anyone could participate, it got off the ground without convincing a bank to run it. But because anyone could participate, there was no privacy: everyone could download the database of payments. And we couldn’t just use an e-cash scheme, as that required someone to keep a secret signing key, and the entire point of Bitcoin was that no one had to be trusted.
This is where Zerocoin, Zerocash, and Zcash come in. They replaced the e-cash system with a zero-knowledge proof and, this fact is not well understood by many, strengthened the privacy of e-cash schemes by giving the recipient full privacy even if the bank was malicious.
Tom D retweeted
Institutional custody. Private markets. Onchain credit.
One of those is us. The other two are why we’re excited about what @edeldotfinance is building on @CantonNetwork.
A significant step forward for Edel.
We're proud to announce our partnership with @Anchorage, a leading institutional digital asset custody provider.
Institutional custody. Private markets. On-chain credit.
The foundations of a new financial market are coming together on @CantonNetwork.
Tom D retweeted
Retail stablecoin adoption came bottom up. Institutional adoption is coming top down.
@sergiofly at @gftn_official Tbilisi: "Every global bank we talk to has a plan for tokenized money, and the next wave is interbank settlement and cross border nostro accounts moving in stablecoins."
Tom D retweeted
Pesos on one side. Dollars on the other. Anchorage Digital Bank custody underneath both.
MXNB is now custodied across six chains, and USDPT and USAT are live on @Bitso. The US-Mexico stablecoin corridor just got its custody layer.
Learn more ↓
okt.to/KFMT8B
Tom D retweeted
I've been de-Googling and transitioning to encrypted, self-hosted, or privacy-first everything over the last ~2 years.
What I changed and notes:
1) Email: Gmail → @ProtonMail
For personal, this was easy. Everything from my old gmail is autoforwarded to a domain-based email address I own hosted via Proton. If Proton goes away tomorrow, I still own the email and can point it to another, hopefully encrypted, email provider.
For business, this is not yet a viable option mainly due to email deliverability and share docs are not quite as good with Proton yet as Google Docs/ Sheets, etc. Will continue to reevaluate over time.
2) Photos: Google Photos/ iPhotos → @enteio
Tedious but surprisingly easy to do. Always have a local backup of anything you really care about, obviously.
3) Calendar → Proton
I sync my gmail based work calendars into this and personal events are only detailed here. Proton is all I look at.
4) Chrome → @brave
Chromium w/o Google, basically. Seamless transition.
5) Passwords & 2fa → ProtonPass, Yubikey
Stop using your browser
6) Direct Browsing → Firewall + Persistent Rotating VPN
Probably the most technical thing on this list.
7) Network Router / Modem → Owned Router/ Modem
(Bonus: everything got way faster.)
8) Keep Notes & DropBox → @StandardNotes
End-to-end encrypted. Make sure you keep your keys, lock yourself out even they can't help you 😅
9) Podcasts: Spotify → @antennapod
If you're primarily a podcast listener there's no reason to use Apple or Spotify for this - Antenna Pod is seamless, free, no ads. (h/t @WatchmanPrivacy for the rec)
10) YouTube → NewPipe
Android. No ads, faster, and you can download YouTube videos for free to watch offline. (Downside - not sure if this will continue to work when Android gets locked down.)
11) Giving out my email address → Aliases for everything (Proton, @cloaked make this simple)
One-touch "Disable email address" to kill SPAM is nice. It all flows into your inbox so there's no change for you, just puts you back in control.
12) Giving out my phone # → Fake # per service (Cloaked, Voip, etc)
Also a fun way to figure out who resells your # (looking at you, electric company). I've killed my old # and have a new one I don't give out to anyone I would not call in the event of an emergency, but I probably take things to an extreme most people do not.
The biggest privacy "levers" are the simplest and don't require an app transition at all - stop sharing your PII - esp your address, personal email, mobile #.
Don't centralize your entire life with 1 company (Google, Apple).
--
This only scratches the surface, but sharing to illustrate that you can avoid giving a single corporation or two control over your digital life.
As we move from a world of creepy-but-mostly-benign-surveillance‑based business models to ubiquitous data sharing, warrantless surveillance and centralization - choosing free/open-source software and decentralizing the tech you use is a vote for personal autonomy.
The tradeoff to convenience is that it almost always comes at the cost of freedom.
Tom D retweeted
Anchorage Digital Bank is bringing federally regulated stablecoins to @Securitize, the world's largest tokenization platform.
Securitize mints and redeems directly with Anchorage Digital Bank, which also handles custody and settlement.
One federally chartered bank, from mint to redemption.
🔗okt.to/2PLhOS
Tom D retweeted
🚨DEFCON 1🚨
In a few hours, a critical vulnerability that affects ~70% of web sites will be disclosed. It allows an attacker to upload and execute arbitrary code.
It's probably best if you stop browsing the internet for the rest of the week.
teapawt.net/ThePHPF/status/2112633…
The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2.
PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.
Readers added context they thought people might want to know
These are server-side PHP RCE vulnerabilities for which web hosts/admins should prepare to patch per official notice; general users face no direct need to stop browsing. PHP detected on ~69% of sites with known server-side language.
php.net/archive/2026.p…
w3techs.com/technologies/d…
cert.europa.eu/publications/s…
sansec.io/research/php2s…
arstechnica.com/security/2026/…
If they were legally allowed to pay yield, stablecoins would optimize returns natively and effortlessly.
The new Ledger Atom.
Powerful like a gorilla, yet soft and yielding like a nerf ball.
youtube.com/watch?v=7A2AJV_M…
How can any business that gives all its employees access to Cowork (and no other LLMs) think they are actually being innovative?