🚨Reminder: Go back and look at your Bookmarks. FUCK they are good. Some outdated but we all save bangers!
chingow.icp retweeted
50+ people have attacked internet-computer:native
@BobbyO_ challenged them to a debate
ZERO accepted
Instead they BLOCK, cower in fear & deceive those who don’t know better
If ICP is so bad, this is an EASY task
DEFEND YOUR COIN
PROVE ICP WRONG
Spoiler alert: THEY CAN’T
chingow.icp retweeted
I wanted to test if a Solana program with no source available could be pulled from the chain and reverse engineered into a byte identical open source version
So I took the daosfun contract and did just that
Found a critical security vulnerability in the mainnet program too, oops!
All smart contracts can be perfectly reverse engineered now
There is no security by obscurity anymore
github.com/lalalune/daosfun-…
chingow.icp retweeted
This will be an interesting week coming up ...
chingow.icp retweeted
NEAR spends $150–200M a year in inflationary rewards to secure its L1.
For what? To use it as a settlement ledger for NEAR Intents, recording and settling the results of cross-chain swaps. Perhaps 50–100K transactions a day, each generating fractions of a cent in fees.
I’m planning to dig deeper into everything NEAR is building and why it needs a token.
$ICP vs $NEAR Just embarrassing for @NEARFoundation and @ilblackdragon.
Not only did they ship a sloppy copy of $ICP tech as a bolted on permissioned MPC, they bragged about it the entire time. (TEMU Web3)
⚠️feb 2024 "a new kind of threshold signature protocol" key resharing presented as new.
@dfinity published it Mar 2021 and @dominic_w personally explained it to Illia on reddit in may 2021. 🚨
⚠️mar 2024 "first of its kind" chain-key BTC signing live on ICP dec 2022.🚨
⚠️aug 2024 "no other signing network lets smart contracts sign on any chain" $ICP canisters signing $BTC since dec 2022, ETH since dec 2023.
⚠️aug 2024 Mainnet launch: illia calls it "a major innovation" @dfinity signing design was published by Groth & Shoup in apr 2022.🚨
⚠️jun 2026 "the only protocol that can trigger native BTC/ETH with threshold cryptography" $ICP both, since 2022/2023. 🚨
⚠️feb 2026: NEAR One "arrived at a vetKeys like design without knowing about it" vetKeys on ICP jun 2025, and NEAR own 2023 requirements doc links the @dfinity vetKeys paper.🚨
Watch the video. If any of it is false, i’d like to know which part. (follow @thebasedgiant the research and production is top tier)
chingow.icp retweeted
Replying to @thebasedgiant @dominic_w
@dominic_w look at this dom, Based is showing some quintessential facts
chingow.icp retweeted
$NEAR accuses $ICP of spreading FUD and lies, but the factual reality says otherwise.
Everything @dominic_w says checks out against public receipts online.
NEAR's own records show where their "unique" tech came from.
Here's the timeline:
1/16 👇
chingow.icp retweeted
A TON OF THINGS HAPPENED IN THE STOCK MARKET TODAY.
Here's a full recap:
1. NEAR Protocol near:native was identified as the most at-risk crypto protocol for PHP hacks. Crypto centric funds are having internal discussions on if the protocol is even solvent at this stage. The NSA recommends pulling all funds off NEAR Protocol IMMEDIATELY.
2. SpaceX $SPCX reported a massive Q3 2026, with revenue surging 161% YoY to $14.6B, while EPS reached $0.35 and net income totaled $4.4B. Adjusted EBITDA jumped 306% YoY to $8.8B, with operating cash flow of $13.1B and capital expenditures of $19.6B, highlighting the scale of the company's infrastructure investments. By segment, Space revenue grew 6% to $1.8B, Connectivity revenue increased 69% to $5.2B, and Space Intelligence (SI) revenue skyrocketed 830% to $7.6B, becoming the company's largest revenue contributor. Elon Musk also outlined aggressive expansion plans for AI compute, saying SpaceX could potentially have 20 GW of SI capacity online by the end of 2027, although he acknowledged that outcome is unlikely. Musk added that he would be surprised if SpaceX deployed less than 13 GW of compute capacity by the end of next year, underscoring the company's ambitions in large-scale AI infrastructure.
3. Anthropic’s draft IPO prospectus reportedly reveals explosive growth alongside unprecedented AI infrastructure commitments, with H1 2026 revenue surging nearly 15x YoY to $16.3B, up from $1.1B, while computing expenses climbed to nearly $9B. The company recorded an $80.7B net loss, although approximately $72B came from accounting adjustments tied to convertible notes and other financing instruments rather than direct operating expenses. Anthropic has reportedly committed roughly $450B to long-term cloud contracts, plus more than $160B for Google-designed AI chips through Broadcom $AVGO, with additional negotiations potentially pushing total computing commitments toward $750B. Major suppliers include Google $GOOGL ($111B), Amazon $AMZN ($110B), Microsoft $MSFT ($31B), and Nscale and Lambda (up to $86B), while the prospectus also highlights risks around customer concentration, power availability, infrastructure execution, and AI-related liability. Anthropic is reportedly preparing for a potential IPO at a valuation approaching $2T, underscoring the extraordinary scale of both the revenue opportunity and capital requirements facing frontier AI developers.
4. Supermicro $SMCI significantly raised its preliminary Q1 FY2027 revenue guidance to $18.5B–$19.5B, up from its previous outlook of $14.5B–$15.5B, representing a 27% increase at the midpoint. The company attributed the stronger outlook to accelerating demand for AI infrastructure platforms, reflecting continued investment in next-generation data center systems. Supermicro also raised its expected gross margin to 12.0%–12.5%, up from 10.4%–10.8%, citing a more favorable customer and product mix. The combination of sharply higher revenue expectations and improving margins suggests stronger operating leverage as demand for AI computing infrastructure continues to expand.
WALL STREET IS THE GREATEST SHOW ON EARTH.
chingow.icp retweeted
Been developer in $ICP since last 4-5years and $NEAR as well, Im very well aware about dfinity’s chain key signatures and ecdsa work and when Near announced Chain Abstraction there was a lot of buzz back then as well that its same as dfinity tech.
But i wasn’t aware that its dfinity proprietary work and there can be legal issues as well.
Things are surely getting interesting here!
chingow.icp retweeted
The algorithm NEAR has been running on for two and a half years is patented. They also took vetKeys, it looks like, but that's not. Obviously if you're mining the repos, research, and work of competitors, without talking to them, referencing them, etc, this is a risk you take.
chingow.icp retweeted
Never forget $ICP fam
ICP's reported TPS numbers are fake! ⚠️
They claim 6k+ TPS, but in reality, ICP only does 0.4 TPS. It is a ghost chain!
By counting basic chain functions as TXs, they are fraudulently misleading the public
Do not be fooled; there is real usage in crypto, but ICP is not it: 🧵
ICP's foundation, DFINITY, is again caught red-handed lying to the public. This time to a preposterous degree:
The Lie:
The 6k TPS figure comes from DFINITY's own official website. Here comes the kicker: 4k of that "TPS" are read-only queries!
The remaining 2k "TPS" are application steps, something ALL other smart contract chains have, but no other blockchain actually counts as TPS. These include contract-to-contract calls, timers, replies & heartbeats. ICP's leadership counts all of these as "TPS" today
The Truth:
Once we subtract all of those phony forms of TPS, ICP ends up with a mere 0.4 TPS, or 0.7 TPS if we also counted every token ledger
That means DFINITY is inflating the usage of ICP by a whopping factor of x16245
All while the biggest user of ICP today is DFINITY's own subnet where they host their apps! The ckBTC & ckETH minters, along with their ETH & SOL relays. Together, produce 31.5% of this fraudulent TPS count
One Example:
There was a particularly interesting incident in 2022 when a developer was loading a database into his app at less than one call a second
DFINITY's own dashboard showed his subnet doing 1.3k Transaction Per Second, a third of the network's usage that week
The developer then went on to the forum to ask how that was possible. The ICP engineer frankly explained it:
"Each upload put 500 records into three indexes, and the code did each insert as a call from the program to itself. Every call counts, and every reply to a call counts again. So one upload became about 3,000 "transactions". Written as one batched call, the same work would have shown "500x fewer transactions".
Following that up with one of the most damning statements in this case:
"DFINITY's own benchmark had deliberately left such messages out, because counting them "might have been deemed as cheating (after all we care about user-triggered transactions rather than artificially generated traffic)".
DFINITY's own dashboard counts them anyway & still does to this day. On this day, the 21st of October 2026, replies to calls between programs were 57 percent of the "update" count! This mechanism is also not rate-limited at all
In conclusion, their own engineer said counting internal messages would be cheating in a benchmark; their own dashboard counts them to this day; that is the number they sell as TPS! Under ICP accounting, 1 TPS turns into 1.3k "TPS". Now that is a fraudulent & misleading design!
Discrepencies
That is how they can claim to do "6k TPS" while only bringing in less than 7k of fees per day, while its own "Internet Identity" ICP's login system registers a mere 3112 users in the last day
Their physical presence in our ecosystem is also not at all congruent with their claim of being the second most used blockchain in the world
Such inconsistencies are hard to reconcile. Which is why this expose was needed. As it turns out, they have been straight-up lying about their usage this entire time!
Chainspect
Why Chainspect, the blockchain explorer & metrics tracker, would unquestioningly repeat these lies. Taking its data directly from DFINITY's API is unknown
Chain Inspect is not a registered company & for that reason & more, I was unable to find any connection to DFINITY, but it cannot be ruled out. They claim to be fiercely independent
Chain Inspect only reports the 2k "TPS" figure, but that is still wildly misleading
Especially since they do carry out more due diligence with other chains, such as by subtracting consensus messages in SOL, for example, as they very well should
Weirdly, their own policy demands that they adjust their figures accordingly:
"We aim to include only user-initiated transactions and exclude system ones, to enable fair comparison of different networks (e.g. for Solana we exclude “voting” transactions related to their custom consensus mechanism)."
As a community, we need to point the finger here & ask @chainspect_app to update their policy on how they count ICP's "TPS".
The correct number is below 1; reporting 2k+ instead is wildly misleading
Do better, Chain Inspect! We are kindly holding you accountable today, as your website & service are otherwise great!
Conclusion
ICP is a ghost chain: There is nothing wrong with that, as we all need to start somewhere
However, what is wrong is that they are actively lying about this fact. In the investment world, that is called fraud!
Honesty & integrity matter far more to serious investors, as we are, myself included, willing to invest in "ghost chains", making a bet on a superior team & tech
It is a shame, as ICP could be a great chain if they enshrined their subnets as I have previously recommended. If they also cleaned up their marketing, it could become a real contender
Instead, the community will most likely respond with denial again. Exposing a sickness that is endemic within many small cryptocurrency communities
Groupthink with cult-like dynamics, combined with both financial & peer pressure, creates one hell of a toxic soup
Despite all of the personal attacks that will likely follow this critique, the truth speaks for itself. That is also one of the most wonderful things about crypto
It is open-source code running a transparent blockchain. The scammers & crooks can not hide anymore with sufficient due diligence, of the sort we did here today
To the ICP community, there are genuinely good, smart & well-meaning people there. We should never paint any community with a single brush
For those of you receptive to this critique, I hope it will inspire ICP to clean up its act. Operating with more honesty & integrity is not only the right thing to do. It is also the best possible long-term strategy for success in our industry today
When all is said & done. It is the truth that sets us all free! 🔥
chingow.icp retweeted
Replying to @dominic_w
@dominic_w please understand that this is the result of attacking NEAR, people will come out the woodwork to attack you. Which is fine as long as you’re ready for it, but terrible if you’re not. If you really intended for the predictable consequences of your actions, you would know that your next step will have to be ending Justin’s career via public humiliation. If you are not prepared for that follow through, don’t start the swing.
ICP's reported TPS numbers are fake! ⚠️
They claim 6k+ TPS, but in reality, ICP only does 0.4 TPS. It is a ghost chain!
By counting basic chain functions as TXs, they are fraudulently misleading the public
Do not be fooled; there is real usage in crypto, but ICP is not it: 🧵
ICP's foundation, DFINITY, is again caught red-handed lying to the public. This time to a preposterous degree:
The Lie:
The 6k TPS figure comes from DFINITY's own official website. Here comes the kicker: 4k of that "TPS" are read-only queries!
The remaining 2k "TPS" are application steps, something ALL other smart contract chains have, but no other blockchain actually counts as TPS. These include contract-to-contract calls, timers, replies & heartbeats. ICP's leadership counts all of these as "TPS" today
The Truth:
Once we subtract all of those phony forms of TPS, ICP ends up with a mere 0.4 TPS, or 0.7 TPS if we also counted every token ledger
That means DFINITY is inflating the usage of ICP by a whopping factor of x16245
All while the biggest user of ICP today is DFINITY's own subnet where they host their apps! The ckBTC & ckETH minters, along with their ETH & SOL relays. Together, produce 31.5% of this fraudulent TPS count
One Example:
There was a particularly interesting incident in 2022 when a developer was loading a database into his app at less than one call a second
DFINITY's own dashboard showed his subnet doing 1.3k Transaction Per Second, a third of the network's usage that week
The developer then went on to the forum to ask how that was possible. The ICP engineer frankly explained it:
"Each upload put 500 records into three indexes, and the code did each insert as a call from the program to itself. Every call counts, and every reply to a call counts again. So one upload became about 3,000 "transactions". Written as one batched call, the same work would have shown "500x fewer transactions".
Following that up with one of the most damning statements in this case:
"DFINITY's own benchmark had deliberately left such messages out, because counting them "might have been deemed as cheating (after all we care about user-triggered transactions rather than artificially generated traffic)".
DFINITY's own dashboard counts them anyway & still does to this day. On this day, the 21st of October 2026, replies to calls between programs were 57 percent of the "update" count! This mechanism is also not rate-limited at all
In conclusion, their own engineer said counting internal messages would be cheating in a benchmark; their own dashboard counts them to this day; that is the number they sell as TPS! Under ICP accounting, 1 TPS turns into 1.3k "TPS". Now that is a fraudulent & misleading design!
Discrepencies
That is how they can claim to do "6k TPS" while only bringing in less than 7k of fees per day, while its own "Internet Identity" ICP's login system registers a mere 3112 users in the last day
Their physical presence in our ecosystem is also not at all congruent with their claim of being the second most used blockchain in the world
Such inconsistencies are hard to reconcile. Which is why this expose was needed. As it turns out, they have been straight-up lying about their usage this entire time!
Chainspect
Why Chainspect, the blockchain explorer & metrics tracker, would unquestioningly repeat these lies. Taking its data directly from DFINITY's API is unknown
Chain Inspect is not a registered company & for that reason & more, I was unable to find any connection to DFINITY, but it cannot be ruled out. They claim to be fiercely independent
Chain Inspect only reports the 2k "TPS" figure, but that is still wildly misleading
Especially since they do carry out more due diligence with other chains, such as by subtracting consensus messages in SOL, for example, as they very well should
Weirdly, their own policy demands that they adjust their figures accordingly:
"We aim to include only user-initiated transactions and exclude system ones, to enable fair comparison of different networks (e.g. for Solana we exclude “voting” transactions related to their custom consensus mechanism)."
As a community, we need to point the finger here & ask @chainspect_app to update their policy on how they count ICP's "TPS".
The correct number is below 1; reporting 2k+ instead is wildly misleading
Do better, Chain Inspect! We are kindly holding you accountable today, as your website & service are otherwise great!
Conclusion
ICP is a ghost chain: There is nothing wrong with that, as we all need to start somewhere
However, what is wrong is that they are actively lying about this fact. In the investment world, that is called fraud!
Honesty & integrity matter far more to serious investors, as we are, myself included, willing to invest in "ghost chains", making a bet on a superior team & tech
It is a shame, as ICP could be a great chain if they enshrined their subnets as I have previously recommended. If they also cleaned up their marketing, it could become a real contender
Instead, the community will most likely respond with denial again. Exposing a sickness that is endemic within many small cryptocurrency communities
Groupthink with cult-like dynamics, combined with both financial & peer pressure, creates one hell of a toxic soup
Despite all of the personal attacks that will likely follow this critique, the truth speaks for itself. That is also one of the most wonderful things about crypto
It is open-source code running a transparent blockchain. The scammers & crooks can not hide anymore with sufficient due diligence, of the sort we did here today
To the ICP community, there are genuinely good, smart & well-meaning people there. We should never paint any community with a single brush
For those of you receptive to this critique, I hope it will inspire ICP to clean up its act. Operating with more honesty & integrity is not only the right thing to do. It is also the best possible long-term strategy for success in our industry today
When all is said & done. It is the truth that sets us all free! 🔥
chingow.icp retweeted
Replying to @Justin_Bons
ICP is an asynchronous chain.
On ETH and most other synchronous chains, a call between contracts all take place inside one atomic transaction. That is, on ETH that IS just one atomic transaction.
On ICP, an asynchronous chain, the way it goes is that
1) first a smart contract does some atomic and isolated work - a transaction
2) then to call another contract, it commits its current transaction and makes an async call, that will result in a new atomic transaction in the callee
3) and then there’s yet another atomic transaction in the caller to process the result.
Thus, on ICP that IS three atomic transactions.
That’s not a technicality - this is what the words mean! All you do is carefully explain to the world that you don’t know what a ”transaction” means in a technical discussion.
You accuse far more serious and accomplished engineers and scientists than yourself of lying, while the only thing you do is expose that you are unfamiliar with computer science 101.
chingow.icp retweeted
🚨 Dom’s PhD engineer called NEAR’s privacy a simulation
Got me curious how the two chains compare on plain numbers.
So I ran them through six axes 👇
⚪ Fees per $1B of market cap
→ $ICP : $112K
→ $NEAR : $32K
⚪ Revenue per $1B of market cap
→ ICP : $1.11M a year
→ NEAR : $135K a year
ICP keeps all its fees as revenue. NEAR keeps about 70%.
⚪ TVL
→ NEAR : 3.20% of its cap
→ ICP : 0.66% of its cap
NEAR’s TVL roughly doubled in 90 days. ICP’s slipped 7.5%.
⚪ Stablecoins
→ NEAR : 1.84% of its cap
→ ICP : 0.24% of its cap
⚪ Daily users
→ NEAR : 10.8K per $1B
→ ICP : 2.5K per $1B
⚪ Transactions
→ NEAR : 3.6M per $1B
→ ICP : 595K per $1B
CertiK rates both AA.
NEAR takes it 4 to 2.
ICP earns more per dollar. NEAR gets used more.
The privacy debate can carry on. The usage gap isn’t up for debate.
This is craazy. I asked one of our PhD engineers to look into NEAR *Confidential* Intents wondering how they designed their system. Unredacted, word-for-word, this was his answer 😱😱😱
"Everything I found out about the privacy claims and confidential intents is so bad that it seems almost comical and I cannot believe what I am seeing. Apparently they run a completely separate instance of the protocol, which is called FAR (as an opposite to NEAR), and that has a permissioned operator set. The entire confidentiality claim seems to rest upon the fact that it is a permissioned chain and the nodes are trusted to keep things private, there doesn't seem to be any deep technology behind it and it also does not seem to be open source. The entities running the nodes are also not publicly known.
I almost feel weird writing this because it is so absurdly bad that it feels like ... I don't know ... a simulation? I know the usual level of overpromising in Web3 but this is so many levels beyond believable that it still feels unreal."
chingow.icp retweeted
The wait is over shielded $ICP is now live.
Every transaction is private, even from the node providers running the network. Your send history, balances, and activity stay protected.
We built it to go beyond SEV’s limits, using pure cryptography so proofs are generated in your browser and verified on-chain without exposing anything.
$BTC is coming next.
$ICP #Privacy #ZK #InternetComputer
chingow.icp retweeted
With cloud engines, apps run without cycles, and now, deploying to the shared Internet Computer subnets will be a breeze too. Agents can show users QR codes, so they can pay with their credit cards, avoiding token friction.
ICP is becoming mainstream agentic infrastructure.
chingow.icp retweeted
Nice 🔥 This illustrates how you can build true cryptographic privacy on top of the Internet Computer. There are lots of privacy narrative protocols these days where operators have backdoors, or which rely on weaker hardware-based privacy (TEEs). Here, performance + real privacy
The wait is over shielded $ICP is now live.
Every transaction is private, even from the node providers running the network. Your send history, balances, and activity stay protected.
We built it to go beyond SEV’s limits, using pure cryptography so proofs are generated in your browser and verified on-chain without exposing anything.
$BTC is coming next.
$ICP #Privacy #ZK #InternetComputer





























