Afraj

I love Allah

[Afraj @pinkey70466893]

@Punk2027 DTdi5BuDFhHmKmVj3XqrdgSy89dX9tx15WbnXQ67Pkmj

[Afraj @pinkey70466893]

I am a desperate father from Bangladesh. My 3yo son, Afraj, is fighting severe Pneumonia. I have no money left for his life-saving treatment. We urgently need $250 (30,000 BDT) to save him. 🙏💔

@BinanceCharity
@cz_binance

[Afraj @pinkey70466893]

I am a desperate father from Bangladesh. My 3yo son, Afraj, is fighting severe Pneumonia. I have no money left for his life-saving treatment. We urgently need $250 to save him. 🙏💔
Please help us! help us!
My USDT (BEP20) Wallet Addres:0x0d30b5c6f33ee68f583c3c0aa95795576cedd858

[Gates Foundation @gatesfoundation]

Three big goals. One shared future.

Haven’t had a chance to read @MSuzman’s annual letter just yet? Here are three things you should know.👇
Read the letter: https://t.co/3hap23LNoJ

[Afraj @pinkey70466893]

My 3year old son Afraj is fighting severe Pneumonia. I have no money left for his treatment. We need $250 (30,000 BDT) urgently to save his life. Please help a desperate father! 💔🙏My USDT (BEP20) Wallet Address:0x0d30b5c6f33ee68f583c3c0aa95795576cedd858
🙏🙏🙏🙏🙏🙏🙏🙏🙏😭😭😭

[vitalik.eth @VitalikButerin]

Now, scaling.

There are two buckets here: short-term and long-term.

Short term scaling I've written about elsewhere. Basically:

* Block level access lists (coming in Glamsterdam) allow blocks to be verified in parallel.
* ePBS (coming in Glamsterdam) has many features, of which one is that it becomes safe to use a large fraction of each slot (instead of just a few hundred milliseconds) to verify a block
* Gas repricings ensure that gas costs of operations are aligned with the actual time it takes to execute them (plus other costs they impose). We're also taking early forays into multidimensional gas, which ensures that different resources are capped differently. Both allow us to take larger fractions of a slot to verify blocks, without fear of exceptional cases.

There is a multi-stage roadmap for multidimensional gas.

First, in Glamsterdam, we separate out "state creation" costs from "execution and calldata" costs. Today, an SSTORE that changes a slot from nonzero -> nonzero costs 5000 gas, an SSTORE that changes zero -> nonzero costs 20000. One of the Glamsterdam repricings greatly increases that extra amount (eg. to 60000); our goal doing this + gas limit increases is to scale execution capacity much more than we scale state size capacity, for reasons I've written before ( https://t.co/7nL9qOQYnm ). So in Glamsterdam, that SSTORE will charge 5000 "regular" gas and (eg.) 55000 "state creation gas".

State creation gas will NOT count toward the ~16 million tx gas cap, so creating large contracts (larger than today) will be possible.

One challenge is: how does this work in the EVM? The EVM opcodes (GAS, CALL...) all assume one dimension. Here is our approach. We maintain two invariants:

* If you make a call with X gas, that call will have X gas that's usable for "regular" OR "state creation" OR other future dimensions
* If you call the GAS opcode, it tells you you have Y gas, then you make a call with X gas, you still have at least Y-X gas, usable for any function, _after_ the call to do any post-operations

What we do is, we create N+1 "dimensions" of gas, where by default N=1 (state creation), and the extra dimension we call "reservoir". EVM execution by default consumes the "specialized" dimensions if it can, and otherwise it consumes from reservoir. So eg. if you have (100000 state creation gas, 100000 reservoir), then if you use SSTORE to create new state three times, your remaining gas goes (100000, 100000) -> (45000, 95000) -> (0, 80000) -> (0, 20000). GAS returns reservoir. CALL passes along the specified gas amount from the reservoir, plus _all_ non-reservoir gas.

Later, we switch to multi-dimensional *pricing*, where different dimensions can have different floating gas prices. This gives us long-term economic sustainability and optimality (see https://t.co/KiiDugo4OA ). The reservoir mechanism solves the sub-call problem at the end of that article.

Now, for long-term scaling, there are two parts: ZK-EVM, and blobs.

For blobs, the plan is to continue to iterate on PeerDAS, and get it to an eventual end-state where it can ideally handle ~8 MB/sec of data. Enough for Ethereum's needs, not attempting to be some kind of global data layer. Today, blobs are for L2s. In the future, the plan is for Ethereum block data to directly go into blobs. This is necessary to enable someone to validate a hyperscaled Ethereum chain without personally downloading and re-executing it: ZK-SNARKs remove the need to re-execute, and PeerDAS on blobs lets you verify availability without personally downloading.

For ZK-EVM, the goal is to step up our "comfort" relying on it in stages:

* Clients that let you participate as an attester with ZK-EVMs will exist in 2026. They will not be safe enough to allow the network to run on them, but eg. 5% of the network relying on them will be ok. (If the ZK-EVM breaks, you *will not* be slashed, you'll just have a risk of building on an invalid block and losing revenue)
* In 2027, we'll start recommending for a larger minority of the network to run on ZK-EVMs, and at the same time full focus will be on formally verifying, maximizing their security, etc. Even 20% of the network running ZK-EVMs will let us greatly increase the gaslimit, because it allows gas limits to greatly increase while having a cheap path for solo stakers, who are under 20% anyway.
* When ready, we move to 3-of-5 mandatory proving. For a block to be valid, it would need to contain 3 of 5 types of proofs from different proof systems. By this point, we would expect that all nodes (except nodes that need to do indexing) will rely on ZK-EVM proofs.
* Keep improving the ZK-EVM, and make it as robust, formally verified, etc as possible. This will also start to involve any VM change efforts (eg. RISC-V)
https://t.co/NQ3JFLe8Gd

[Afraj @pinkey70466893]

Please help me,
My 3year son, Afraj, is fighting severe Pneumonia at Lohagara City Hospital. I’ve run out of funds for his treatment. 💔

We urgently need $250 (30,000 BDT) to save his life. Please, if you can, help this desperate father. Every dollar counts. 🙏

[vitalik.eth @VitalikButerin]

Now, scaling.

There are two buckets here: short-term and long-term.

Short term scaling I've written about elsewhere. Basically:

* Block level access lists (coming in Glamsterdam) allow blocks to be verified in parallel.
* ePBS (coming in Glamsterdam) has many features, of which one is that it becomes safe to use a large fraction of each slot (instead of just a few hundred milliseconds) to verify a block
* Gas repricings ensure that gas costs of operations are aligned with the actual time it takes to execute them (plus other costs they impose). We're also taking early forays into multidimensional gas, which ensures that different resources are capped differently. Both allow us to take larger fractions of a slot to verify blocks, without fear of exceptional cases.

There is a multi-stage roadmap for multidimensional gas.

First, in Glamsterdam, we separate out "state creation" costs from "execution and calldata" costs. Today, an SSTORE that changes a slot from nonzero -> nonzero costs 5000 gas, an SSTORE that changes zero -> nonzero costs 20000. One of the Glamsterdam repricings greatly increases that extra amount (eg. to 60000); our goal doing this + gas limit increases is to scale execution capacity much more than we scale state size capacity, for reasons I've written before ( https://t.co/7nL9qOQYnm ). So in Glamsterdam, that SSTORE will charge 5000 "regular" gas and (eg.) 55000 "state creation gas".

State creation gas will NOT count toward the ~16 million tx gas cap, so creating large contracts (larger than today) will be possible.

One challenge is: how does this work in the EVM? The EVM opcodes (GAS, CALL...) all assume one dimension. Here is our approach. We maintain two invariants:

* If you make a call with X gas, that call will have X gas that's usable for "regular" OR "state creation" OR other future dimensions
* If you call the GAS opcode, it tells you you have Y gas, then you make a call with X gas, you still have at least Y-X gas, usable for any function, _after_ the call to do any post-operations

What we do is, we create N+1 "dimensions" of gas, where by default N=1 (state creation), and the extra dimension we call "reservoir". EVM execution by default consumes the "specialized" dimensions if it can, and otherwise it consumes from reservoir. So eg. if you have (100000 state creation gas, 100000 reservoir), then if you use SSTORE to create new state three times, your remaining gas goes (100000, 100000) -> (45000, 95000) -> (0, 80000) -> (0, 20000). GAS returns reservoir. CALL passes along the specified gas amount from the reservoir, plus _all_ non-reservoir gas.

Later, we switch to multi-dimensional *pricing*, where different dimensions can have different floating gas prices. This gives us long-term economic sustainability and optimality (see https://t.co/KiiDugo4OA ). The reservoir mechanism solves the sub-call problem at the end of that article.

Now, for long-term scaling, there are two parts: ZK-EVM, and blobs.

For blobs, the plan is to continue to iterate on PeerDAS, and get it to an eventual end-state where it can ideally handle ~8 MB/sec of data. Enough for Ethereum's needs, not attempting to be some kind of global data layer. Today, blobs are for L2s. In the future, the plan is for Ethereum block data to directly go into blobs. This is necessary to enable someone to validate a hyperscaled Ethereum chain without personally downloading and re-executing it: ZK-SNARKs remove the need to re-execute, and PeerDAS on blobs lets you verify availability without personally downloading.

For ZK-EVM, the goal is to step up our "comfort" relying on it in stages:

* Clients that let you participate as an attester with ZK-EVMs will exist in 2026. They will not be safe enough to allow the network to run on them, but eg. 5% of the network relying on them will be ok. (If the ZK-EVM breaks, you *will not* be slashed, you'll just have a risk of building on an invalid block and losing revenue)
* In 2027, we'll start recommending for a larger minority of the network to run on ZK-EVMs, and at the same time full focus will be on formally verifying, maximizing their security, etc. Even 20% of the network running ZK-EVMs will let us greatly increase the gaslimit, because it allows gas limits to greatly increase while having a cheap path for solo stakers, who are under 20% anyway.
* When ready, we move to 3-of-5 mandatory proving. For a block to be valid, it would need to contain 3 of 5 types of proofs from different proof systems. By this point, we would expect that all nodes (except nodes that need to do indexing) will rely on ZK-EVM proofs.
* Keep improving the ZK-EVM, and make it as robust, formally verified, etc as possible. This will also start to involve any VM change efforts (eg. RISC-V)
https://t.co/NQ3JFLe8Gd

[vitalik.eth @VitalikButerin]

Now, scaling.

There are two buckets here: short-term and long-term.

Short term scaling I've written about elsewhere. Basically:

* Block level access lists (coming in Glamsterdam) allow blocks to be verified in parallel.
* ePBS (coming in Glamsterdam) has many features, of which one is that it becomes safe to use a large fraction of each slot (instead of just a few hundred milliseconds) to verify a block
* Gas repricings ensure that gas costs of operations are aligned with the actual time it takes to execute them (plus other costs they impose). We're also taking early forays into multidimensional gas, which ensures that different resources are capped differently. Both allow us to take larger fractions of a slot to verify blocks, without fear of exceptional cases.

There is a multi-stage roadmap for multidimensional gas.

First, in Glamsterdam, we separate out "state creation" costs from "execution and calldata" costs. Today, an SSTORE that changes a slot from nonzero -> nonzero costs 5000 gas, an SSTORE that changes zero -> nonzero costs 20000. One of the Glamsterdam repricings greatly increases that extra amount (eg. to 60000); our goal doing this + gas limit increases is to scale execution capacity much more than we scale state size capacity, for reasons I've written before ( https://t.co/7nL9qOQYnm ). So in Glamsterdam, that SSTORE will charge 5000 "regular" gas and (eg.) 55000 "state creation gas".

State creation gas will NOT count toward the ~16 million tx gas cap, so creating large contracts (larger than today) will be possible.

One challenge is: how does this work in the EVM? The EVM opcodes (GAS, CALL...) all assume one dimension. Here is our approach. We maintain two invariants:

* If you make a call with X gas, that call will have X gas that's usable for "regular" OR "state creation" OR other future dimensions
* If you call the GAS opcode, it tells you you have Y gas, then you make a call with X gas, you still have at least Y-X gas, usable for any function, _after_ the call to do any post-operations

What we do is, we create N+1 "dimensions" of gas, where by default N=1 (state creation), and the extra dimension we call "reservoir". EVM execution by default consumes the "specialized" dimensions if it can, and otherwise it consumes from reservoir. So eg. if you have (100000 state creation gas, 100000 reservoir), then if you use SSTORE to create new state three times, your remaining gas goes (100000, 100000) -> (45000, 95000) -> (0, 80000) -> (0, 20000). GAS returns reservoir. CALL passes along the specified gas amount from the reservoir, plus _all_ non-reservoir gas.

Later, we switch to multi-dimensional *pricing*, where different dimensions can have different floating gas prices. This gives us long-term economic sustainability and optimality (see https://t.co/KiiDugo4OA ). The reservoir mechanism solves the sub-call problem at the end of that article.

Now, for long-term scaling, there are two parts: ZK-EVM, and blobs.

For blobs, the plan is to continue to iterate on PeerDAS, and get it to an eventual end-state where it can ideally handle ~8 MB/sec of data. Enough for Ethereum's needs, not attempting to be some kind of global data layer. Today, blobs are for L2s. In the future, the plan is for Ethereum block data to directly go into blobs. This is necessary to enable someone to validate a hyperscaled Ethereum chain without personally downloading and re-executing it: ZK-SNARKs remove the need to re-execute, and PeerDAS on blobs lets you verify availability without personally downloading.

For ZK-EVM, the goal is to step up our "comfort" relying on it in stages:

* Clients that let you participate as an attester with ZK-EVMs will exist in 2026. They will not be safe enough to allow the network to run on them, but eg. 5% of the network relying on them will be ok. (If the ZK-EVM breaks, you *will not* be slashed, you'll just have a risk of building on an invalid block and losing revenue)
* In 2027, we'll start recommending for a larger minority of the network to run on ZK-EVMs, and at the same time full focus will be on formally verifying, maximizing their security, etc. Even 20% of the network running ZK-EVMs will let us greatly increase the gaslimit, because it allows gas limits to greatly increase while having a cheap path for solo stakers, who are under 20% anyway.
* When ready, we move to 3-of-5 mandatory proving. For a block to be valid, it would need to contain 3 of 5 types of proofs from different proof systems. By this point, we would expect that all nodes (except nodes that need to do indexing) will rely on ZK-EVM proofs.
* Keep improving the ZK-EVM, and make it as robust, formally verified, etc as possible. This will also start to involve any VM change efforts (eg. RISC-V)
https://t.co/NQ3JFLe8Gd

[Afraj @pinkey70466893]

@MrBeast My 3yr old son Afraj is fighting severe Pneumonia. I have no money left for his treatment. We need $250 (30,000 BDT) urgently to save his life. Please help a desperate father! 💔🙏My USDT (BEP20) Wallet Address:0x0d30b5c6f33ee68f583c3c0aa95795576cedd858
@MrBeast
🙏🙏🙏🙏🙏🙏🙏

[Afraj @pinkey70466893]

My 3yr old son Afraj is fighting severe Pneumonia. I have no money left for his treatment. We need $250 (30,000 BDT) urgently to save his life. Please help a desperate father! 💔🙏My USDT (BEP20) Wallet Address:0x0d30b5c6f33ee68f583c3c0aa95795576cedd858
😭😭😭😭🙏🙏🙏🙏🙏

[MrBeast @MrBeast]

Just wired the Beast Games 2 winner $5,000,000 😁

[MrBeast @MrBeast]

Just wired the Beast Games 2 winner $5,000,000 😁

[Afraj @pinkey70466893]

My 3yr old son Afraj is fighting severe Pneumonia. I have no money left for his treatment. We need $250 (30,000 BDT) urgently to save his life. Please help a desperate father! 💔🙏My USDT (BEP20) Wallet Address:0x0d30b5c6f33ee68f583c3c0aa95795576cedd858

[Ben Shapiro @benshapiro]

On the show today:

The Daily Wire drops the bombshell news that we’re in production on a new action flick with cancelled star Jonathan Majors;

Gavin Newsom says California is built on genocided land;

and Hillary talks Epstein with Congress.

Watch here:
https://t.co/arTeFyGLw3

[Ben Shapiro @benshapiro]

On the show today:

The Daily Wire drops the bombshell news that we’re in production on a new action flick with cancelled star Jonathan Majors;

Gavin Newsom says California is built on genocided land;

and Hillary talks Epstein with Congress.

Watch here:
https://t.co/arTeFyGLw3

[Afraj @pinkey70466893]

My 3yr old son Afraj is fighting severe Pneumonia. I have no money left for his treatment. We need $250 (30,000 BDT) urgently to save his life. Please help a desperate father! 💔🙏My USDT (BEP20) Wallet Address:0x0d30b5c6f33ee68f583c3c0aa95795576cedd858

[Not Elon Musk @ElonMuskAOC]

I gave you $1,000,000.

What’s the first thing you buy?

[Not Elon Musk @ElonMuskAOC]

I gave you $1,000,000.

What’s the first thing you buy?

[Afraj @pinkey70466893]

My 3yr old son Afraj is fighting severe Pneumonia. I have no money left for his treatment. We need $250 (30,000 BDT) urgently to save his life. Please help a desperate father! 💔🙏My USDT (BEP20) Wallet Address:0x0d30b5c6f33ee68f583c3c0aa95795576cedd858

[MELANIA TRUMP @MELANIATRUMP]

MELANIA, the film, exclusively in theaters worldwide on January 30th, 2026.

[Afraj @pinkey70466893]

My 3yo son, Afraj, is fighting severe Pneumonia at Lohagara City Hospital. I’ve run out of funds for his treatment.
My USDT (BEP20) Wallet Address:
0x0d30b5c6f33ee68f583c3c0aa95795576cedd858
#MedicalEmergency #HelpSaveALife #Pneumonia #CryptoDonations #Charity
@cz_binance

[Afraj @pinkey70466893]

@jiay_0066 Good project

[wangjiayi @jiay_0066]

와… 공작무·뱀춤은 자연 모사라면 〈만마분등〉은 인간 + AI 콜라보로 만들어진 신화급 공간임. 천문AI가 야성과 생명을 공간에 풀어주고, 무용수 표현까지 바꾸다니… 솔직히 레벨 진짜 높음^^

#양리핑_천마무 #양리핑_AI인가요 #양리핑_천문AI

[FoxiGrow @FoxiGrow]

**Major Update: Link Your Google Account – Secure Your FoxiGrow Forever**

Community feedback highlighted a real issue: Telegram accounts can get frozen or deleted, locking users out of FoxiGrow and risking loss of progress, USDT balances, and more.

Our engineers worked overtime and just rolled out **Google Account Binding**!
Once you link your Google account:
- Even if your Telegram gets banned or lost
- Simply log in with a **new Telegram account**
- Verify via Google → **all your data transfers instantly** (tasks, earnings, referrals, FG coin balance — everything restored!)

**Do it now**: Go to @FoxiGrowbot→ “Link Google Account”

FoxiGrow is built for the long haul — aiming to run strong for 20+ years. Account security comes first. Binding Google gives you true, reliable protection for your assets and progress.

Before rolling out more high-value tasks, we’re focusing on system hardening, better verification, and performance upgrades to keep everything stable and trustworthy.

Thank you for your patience and support — we’re committed to making FoxiGrow the most reliable long-term earning platform out there! 🦊💰

Let’s keep building safely and earning steadily! 🚀

[FoxiGrow @FoxiGrow]

The Social-to-Earn USDT Revolution is HERE! 🔥
@FoxiGrow turns your likes, retweets & simple tasks into real crypto rewards.
✅ Super easy tasks
✅ Instant USDT payouts
✅ Tons of events & USDT rewards waiting for you!
Start now → 🦊 https://t.co/fmMRNmWRst

📢 Community already earned $10,500 USDT total! 💰
Next 3 months? We're aiming for 5-10x growth 🚀

Who's joining the grind today? 👇
#MakeMoneyOnline #SideHustle #EarnCrypto #USDT #TelegramMiniApp #SocialToEarn