Today, June 2, is the close of Treasury’s GENIUS Act comment period on state regulatory equivalence.
The big picture is now clear: the GENIUS Act is law, and the remaining fight is implementation. FinCEN/OFAC and FDIC comments close June 9, NCUA closes July 17, and the statutory backstop is January 18, 2027.
We think compliant stablecoins need more than legal wrappers. They need cryptographic infrastructure for policy enforcement, lawful-order response, access control, and auditable operations.
Learn more: https://t.co/2QDQ3qgHUW
If you’re working on stablecoin issuance, compliance, custody, or state/federal implementation, we'd love to connect.
$20 in trading credit, funded straight to your VincentAI account. Not a lottery. Tell us how you trade today — we pick based on your answers.
We're picking up to 50 active traders for a paid pilot of VincentAI — an AI that reads millions of tweets, tracks thousands of analysts, and builds you a daily trade plan with entry, stop-loss, and take-profit pre-set. Crypto, stocks, forex, commodities. Up to 50x leverage.
Apply by 4 June → https://t.co/FyIHtb45lF
4/ Put it together and you can:
- sign with keys secured by on-chain rules
- decrypt only when an on-chain condition passes
- run code that can hold keys and call APIs
- return results people can verify cryptographically
One API. No infra to babysit.
Docs: https://t.co/jCzdIRGAAH
You don’t manage private keys.
You make API calls.
Lit Chipotle gives you confidential compute and key management behind one API. It’s been live for six weeks, and builders are starting to do some cool, useful stuff with it.
Here’s the short version in 4 replies ↓
3/ Lit Actions are immutable JavaScript, identified by IPFS CID.
You submit code. Chipotle computes the CID, checks integrity, then runs it in the TEE with access to derived key material.
You don’t have to upload to IPFS, though publishing helps anyone verify it independently.
Even with AI agents, there's more to do than time when starting a company.
So we built a skill that acts like a proactive cofounder.
It's plugged into your inbox, docs, code, cloud, and accounts. It runs ops, ships work, moves the company forward while you sleep.
Looking for a few founders to test it. Reply or DM!
Polymarket pays 20% on a winning call. Vincent pays 200%. $100 controls a $5,000 position. Crypto moves 5% daily — your calls play out in hours, not weeks. One swipe from a CT take to a live trade. https://t.co/HXUv43ofbU
Modern markets are fundamentally extractive
We've spent three years rewiring them from scratch
One core feature is everyone deploying their own bots without code or infra
Here's a first look @SynchronicityHQ We're looking for strategists to test drive. Reply for early access
SCRYPT ID BETA
LAUNCHING TODAY
First Names Free
$1 Litecoin Verification Fee
Manage All Your Scrypt IDs in One Place
Send Litecoin with a link!
Fully non-custodial using @LitProtocol’s API!
Live now at https://t.co/7vbEg29V2Y
Built an MPC-based wallet prototype on top of @Zcash via @LitProtocol.
This is how it works:
Orchard key hierarchy is threshold-encrypted and shared across the Lit Protocol nodes.
Users can access their keys inside a trusted execution environment via Lit Actions. This is a JavaScript runtime.
The main challenge was constructing a Halo2 proof inside a JS-based runtime.
First, I aimed to prove and sign within a single Lit Action call. Compiled Rust Orchard prover into WASM. On my machine, the shielded transfer WASM proof took roughly 20s. The Lit Action version consumed over 30 seconds, the Lit runtime's execution limit.
So, I offloaded the actual proving to a helper Rust server. Now the flow is:
1. Lit Action decrypts the seed, derives keys, and builds the Orchard circuit witness inside the TEE.
2. Lit Action calls the proving server to generate the Halo2 proof.
3. Proof returns to the same Lit Action, which signs and serializes the full transaction.
Spending keys never leave the TEE. The serialized circuit witness is exposed to the helper server, which reveals transaction details like amounts/recipients.
To mitigate, run the proving server in a TEE as well.
In the screenshot, you can see the Halo2 Shielded Transfer benchmark when running on the:
- Local M3 Pro with 11 cores: 1s
- Railway (auto-scaling x86): 2.1s
- Phala TEE, 4 vCPU Granite Rapids @ 2.4 GHz, TDX: 17.2s
The TEE is 8.2x slower while 8x more expensive than a standard CPU instance.
The cost of privacy is real, but it's worth it.