DMpay.eth

23 posts

DMpay.eth banner
DMpay.eth

DMpay.eth

@DMpayeth

Pay-To-Message On Ethereum | Connect X | Set Your Price | Get Paid In USDC For DMs | Built On ENS | Ethereum | XMTP

Ethereum Entrou em Şubat 2026
47 Seguindo16 Seguidores
DMpay.eth
DMpay.eth@DMpayeth·
USDC just crossed 64% of stablecoin transaction volume. Visa settles in it. Stripe integrates it. The OCC regulates it. And we built a messaging protocol where USDC is the key to the door. No spam. No bots. No noise. Just wallets talking to wallets @dmpayeth is live. 🟢
English
0
0
0
7
MrBeast
MrBeast@MrBeast·
Feastables x Super Mario Galaxy Movie The Yoshi eggs are 🔥
MrBeast tweet media
English
2.3K
1K
14.6K
1.8M
Bambulu 2.0
Bambulu 2.0@BambuluMen·
If she's tired, polygamy solves it If she's not in the mood, polygamy solves it If she has low libido, polygamy solves it If she's unavailable, polygamy solves it If she's on her period, polygamy solves it If she's in postpartum, polygamy solves it If she's acting funny & trying to deny you sex, polygamy solves it If she won't cook/wants to starve you, polygamy solves it If she's getting complacent, polygamy puts her on her toes If she's unsubmissive, polygamy puts her in her place Polygamy solves everything. You just haven't realised yet.
𝐀𝐬𝐚𝐤𝐲𝐆𝐑𝐍@AsakyGRN

His wife kept telling him she missed her best friend and wanted to spend more time with her. Instead of arguing, the husband married the best friend as a second wife so they could see each other every day. 😭

English
63
286
2.2K
212.5K
DMpay.eth retweetou
@levelsio
@levelsio@levelsio·
💸 @X paid me a reasonable $12,000 to tweet this month $10,511 ad rev share $1,247 subs revenue (= $11,758 per 28 days) = $12,807/month Median X revenue now since X started paying me is @ $9,000/mo If my X account was a business and valued at just these payouts, it would be worth at 10x @ $1,080,000, or at 20x @ $2,160,000 Although I think a bit more if you value the reach
@levelsio tweet media@levelsio tweet media@levelsio tweet media
@levelsio@levelsio

💸 This month my @X payouts reached a new record just a 5 cents shy of $16,000! I think something might have changed as they announced they'd pay creators and counts views in a different way, I think it worked: $12,819 ad rev share $1,865 subs revenue (= $14,684 per 28 days) = $15,995/month Posting on X is finally becoming a real potential income stream 😊👍 This is getting close to passing some of my businesses in revenue which is very cool to see!

English
254
34
1.4K
452.4K
Noah Kagan
Noah Kagan@noahkagan·
You build it. I promote it. Building has never been easier. Getting customers has never been harder. So I’m picking 2 products to promote to our 1,000,000+ entrepreneurs for our 16-year anniversary next Tuesday. Drop your product below. Don’t have one? Build it this weekend and come back.
English
1.1K
28
945
79.8K
MrBeast
MrBeast@MrBeast·
SOMEONE FINALLY FOUND THE $1,000,000 WE HID IN OUR SALESFORCE SUPERBOWL COMMERCIAL LOL
English
2.8K
1.2K
35.6K
4.3M
Logan Paul
Logan Paul@LoganPaul·
@BreidenFehoko Wait so are you down or not bc it sounds like you don’t have the money. I’ll send you same contract as Le’Veon if you’re in for next weekend
English
145
14
1.2K
1.8M
@levelsio
@levelsio@levelsio·
@SahilPanhotra Nope just curious to see what's happening I never get paid to tweet except by @X
English
3
0
12
5K
vitalik.eth
vitalik.eth@VitalikButerin·
One important technical item that I forgot to mention is the proposed switch from Casper FFG to Minimmit as the finality gadget. To summarize, Casper FFG provides two-round finality: it requires each attester to sign once to "justify" the block, and then again to "finalize" it. Minimmit only requires one round. In exchange, Minimmit's fault tolerance (in our parametrization) drops to 17%, compared to Casper FFG's 33%. Within Ethereum consensus discussions, I have always been the security assumptions hawk: I've insisted on getting to the theoretical bound of 49% fault tolerance under synchrony, kept pushing for 51% attack recovery gadgets, came up with DAS to make data availability checks dishonest-majority-resistant, etc. But I am fine with Minimmit's properties, in fact even enthusiastic in some respects. In this post, I will explain why. Let's lay out the exact security properties of both 3SF (not the current beacon chain, which is needlessly weak in many ways, but the ideal 3SF) and Minimmit. "Synchronous network" means "network latency less than 1/4 slot or so", "asynchronous network" means "potentially very high latency, even some nodes go offline for hours at a time". The percentages ("attacker has <33%") refer to percentages of active staked ETH. ## Properties of 3SF Synchronous network case: * Attacker has p < 33%: nothing bad happens * 33% < p < 50%: attacker can stop finality (at the cost of losing massive funds via inactivity leak), but the chain keeps progressing normally * 50% < p < 67%: attacker can censor or revert the chain, but cannot revert finality. If an attacker censors, good guys can self-organize, they can stop contributing to a censoring chain, and do a "minority soft fork" * p > 67%: attacker can finalize things at will, much harder for good guys to do minority soft fork Asynchronous network case: * Attacker has p < 33%: cannot revert finality * p > 33%: can revert finality, at the cost of losing massive funds via slashing ## Properties of Minimmit Synchronous network case: * Attacker has p < 17%: nothing bad happens * 17% < p < 50%: attacker can stop finality (at the cost of losing massive funds via inactivity leak), but the chain keeps progressing normally * 50% < p < 83%: attacker can censor or revert the chain, but cannot revert finality. If an attacker censors, good guys can self-organize, they can stop contributing to a censoring chain, and do a "minority soft fork" * p > 83%: attacker can finalize things at will, much harder for good guys to do minority soft fork Asynchronous network case: * Attacker has p < 17%: cannot revert finality * p > 17%: can revert finality, at the cost of losing massive funds via slashing I actually think that the latter is a better tradeoff. Here's my reasoning why: * The worst kind of attack is actually not finality reversion, it's censorship. The reason is that finality reversion creates massive publicly available evidence that can be used to immediately cost the attacker millions of ETH (ie. billions of dollars), whereas censorship requires social coordination to get around * In both of the above, a censorship attack requires 50% * A censorship attack becomes *much harder* to coordinate around when the censoring attacker can unilaterally finalize (ie. >67% in 3SF, >83% in Minimmit). If they can't, then if the good guys counter-coordinate, you get two non-finalizing chains dueling for a few days, and users can pick on. If they can, then there's no natural schelling point to coordinate soft-forking * In the case of a client bug, the worst thing that can happen is finalizing something bugged. In 3SF, you only need 67% of clients to share a bug for it to finalize, in Minimmit, you need 83%. Basicallly, Minimmit maximizes the set of situations that "default to two chains dueling each other", and that is actually a much healthier and much more recoverable outcome than "the wrong thing finalizing". We want finality to mean final. So in situations of uncertainty (whether attacks or software bugs), we should be more okay with having periods of hours or days where the chain does not finalize, and instead progresses based on the fork choice rule. This gives us time to think and make sure which chain is correct. Also, I think the "33% slashed to revert finality" of 3SF is overkill. If there is even eg. 15 million ETH staking, then that's 5M ($10B) slashed to revert the chain once. If you had $10B, and you are willing to commit mayhem of a type that violates many countries' computer hacking laws, there are FAR BETTER ways to spend it than to attack a chain. Even if your goal is breaking Ethereum, there are far better attack vectors. And so if we have the baseline guarantee of >= 17% slashed to revert finality (which Minimmit provides), we should judge the two systems from there based on their other properties - where, for the reasons I described above, I think Minimmit performs better.
vitalik.eth@VitalikButerin

Finally, the block building pipeline. In Glamsterdam, Ethereum is getting ePBS, which lets proposers outsource to a free permissionless market of block builders. This ensures that block builder centralization does not creep into staking centralization, but it leaves the question: what do we do about block builder centralization? And what are the _other_ problems in the block building pipeline that need to be addressed, and how? This has both in-protocol and extra-protocol components. ## FOCIL FOCIL is the first step into in-protocol multi-participant block building. FOCIL lets 16 randomly-selected attesters each choose a few transactions, which *must* be included somewhere in the block (the block gets rejected otherwise). This means that even if 100% of block building is taken over by one hostile actor, they cannot prevent transactions from being included, because the FOCILers will push them in. ## "Big FOCIL" This is more speculative, but has been discussed as a possible next step. The idea is to make the FOCILs bigger, so they can include all of the transactions in the block. We avoid duplication by having the i'th FOCIL'er by default only include (i) txs whose sender address's first hex char is i, and (ii) txs that were around but not included in the previous slot. So at the cost of one slot delay, only censored txs risk duplication. Taking this to its logical conclusion, the builder's role could become reduced to ONLY including "MEV-relevant" transactions (eg. DEX arbitrage), and computing the state transition. ## Encrypted mempools Encrypted mempools are one solution being explored to solve "toxic MEV": attacks such as sandwiching and frontrunning, which are exploitative against users. If a transaction is encrypted until it's included, no one gets the opportunity to "wrap" it in a hostile way. The technical challenge is: how to guarantee validity in a mempool-friendly and inclusion-friendly way that is efficient, and what technique to use to guarantee that the transaction will actually get decrypted once the block is made (and not before). ## The transaction ingress layer One thing often ignored in discussions of MEV, privacy, and other issues is the network layer: what happens in between a user sending out a transaction, and that transaction making it into a block? There are many risks if a hostile actor sees a tx "in the clear" inflight: * If it's a defi trade or otherwise MEV-relevant, they can sandwich it * In many applications, they can prepend some other action which invalidates it, not stealing money, but "griefing" you, causing you to waste time and gas fees * If you are sending a sensitive tx through a privacy protocol, even if it's all private onchain, if you send it through an RPC, the RPC can see what you did, if you send it through the public mempool, any analytics agency that runs many nodes will see what you did There has recently been increasing work on network-layer anonymization for transactions: exploring using Tor for routing transactions, ideas around building a custom ethereum-focused mixnet, non-mixnet designs that are more latency-minimized (but bandwidth-heavier, which is ok for transactions as they are tiny) like Flashnet, etc. This is an open design space, I expect the kohaku initiative @ncsgy will be interested in integrating pluggable support for such protocols, like it is for onchain privacy protocols. There is also room for doing (benign, pro-user) things to transactions before including them onchain; this is very relevant for defi. Basically, we want ideal order-matching, as a passive feature of the network layer without dependence on servers. Of course enabling good uses of this without enabling sandwiching involves cryptography or other security, some important challenges there. ## Long-term distributed block building There is a dream, that we can make Ethereum truly like BitTorrent: able to process far more transactions than any single server needs to ever coalesce locally. The challenge with this vision is that Ethereum has (and indeed a core value proposition is) synchronous shared state, so any tx could in principle depend on any other tx. This centralizes block building. "Big FOCIL" handles this partially, and it could be done extra-protocol too, but you still need one central actor to put everything in order and execute it. We could come up with designs that address this. One idea is to do the same thing that we want to do for state: acknowledge that >95% of Ethereum's activity doesn't really _need_ full globalness, though the 5% that does is often high-value, and create new categories of txs that are less global, and so friendly to fully distributed building, and make them much cheaper, while leaving the current tx types in place but (relatively) more expensive. This is also an open and exciting long-term future design space. firefly.social/post/lens/8144…

English
239
113
874
262.5K
Nick O’Neill
Nick O’Neill@chooserich·
CRYPTO SELLOFF CONTINUES DESPITE THE MOST BULLISH NEWS EVER!
English
80
55
600
47.2K
vitalik.eth
vitalik.eth@VitalikButerin·
@baseddesigner @dcposch That's something kohaku is doing, turning railgun and other privacy protocols (and more) into an easy-to-use self-contained sdk (last year the target user was browser wallets, now we have to make it work for agents too😄)
English
12
7
50
1.8K
vitalik.eth
vitalik.eth@VitalikButerin·
I think it's healthy for us in the Ethereum world to have a more bold and open mindset to many things, particularly on the application layer and on how we see ourselves in the world. We should not compromise on core properties: censorship resistance, open source, privacy, security (CROPS). We should not have "open mindedness" of the type that leaves people with no confidence of what security properties the L1 will still have one year from now. We should not ask ourselves questions like "do we really need light clients to be able to trustlessly verify correctness of the chain?". But especially on the layer of applications and Ethereum's interface to the world, we should be more willing to radically rethink various concepts and step outside our comfort zone. This includes issues of technological direction, eg. "what if AI basically means that wallets as browser extensions and mobile extensions are dead within a year?" One example last year was the shift to thinking about privacy as a first-class consideration, something we value equally to the other types of security. This implies a radically different Ethereum application stack, because the entire stack so far has not been built around privacy. Great, let's build a radically different Ethereum application stack! An example this year is the growing work on the networking side of privacy, both inside the EF and outside. It includes application-layer issues, eg. "what if the rest of defi is basically just universal futures markets on top of a good decentralized oracle and letting users self-organize on top of that?", and "what if the ideal decentralized oracle is just a SNARK over M-of-N small LLMs over zk-TLSes of some major news sites?" (BTW this is interrelated with the AI issue: one consequence of AI is that it moves "applications" away from being discrete categories of behavior with discrete UIs, and more toward being a continuous space, so "build fewer apps and rely on users to self-organize around them" should inevitably expand as a pattern) One example this year is rethinking from zero the role of L2s, and what kind of L2s are actually most synergistic and additive to Ethereum. It also includes culture. This is a big part of "the whole milady thing" for myself, @AyaMiyagotchi and others. Yes, it's a silly meme. Yes, I find the political takes of some milady partisans cringe and sometimes outright bootlickerish (though other milady partisans are quite the opposite). But the core underlying subtext, the message behind the message, is: rip off the suit and tie. If you have your suit and tie on, be willing to grab the nearest wine glass and spill it all over your suit and tie, so you have no choice but to rip it off and reclaim your body's full flexibility and freedom. Actually imagine yourself doing this the next time you get invited to a richpeopleslop formal gala dinner. Take the preconception that you are "respectable", write it down on a piece of paper, crumble it up and burn it. The psychological baptism of doing this leads to the intellectual baptism of unlocking greater creativity and expanding overton windows. For too long, our algorithm in Ethereum has been: we have this existing ecosystem, what's the logical next step to make it one step better? Now, our algorithm should be: we have this L1 that is amazing and will become more amazing, we have a growing array of tools, both those built within our ecosystem and outside it, what are the most valuable things to build, knowing what we know now? If YOU had to write the section of the 2014 Ethereum whitepaper that talked about applications, and take a first-principles perspective of what makes sense in defi, decentralized social, identity, and elsewhere, what would you write? At least take the step of marking all path-dependence concerns down to zero, pretend for a brief moment that the Ethereum chain today has exactly zero usage and you're the one suggesting or building the first apps, and see what comes out. Do this even if you're the one building today's existing apps. This is how Ethereum can grow back stronger.
English
541
364
2.5K
441.5K
Jake Paul
Jake Paul@jakepaul·
It’s insane how people haven’t learned that NBA, NFL, and other professional athletes aren’t fighters There’s no difference to what Logan would do to the NFL players and to what I did to Nate Robinson Why are we still talking about this😅😅 Sean Strickland worked Maxx Crosby barely trying and Maxx is one of the strongest, biggest, and most athletic in the NFL and SEAN ISNT A BOXER!
English
898
89
3.6K
842.7K
DMpay.eth
DMpay.eth@DMpayeth·
Get paid for DMs. Create your DMpay account for free! Set your price in USDC 💵 Connect your X account share your IPFS profile card. IPFS profile card 👇 ensgianteth.dmpay.eth.link app.dmpay.me
DMpay.eth tweet media
English
0
0
1
502
Michael Saylor
Michael Saylor@saylor·
There isn’t enough Bitcoin for everyone.
English
2.9K
2.2K
21.9K
1.2M