Mr Bonangles

[Simon Andriesz @SAndriesz]

I am the British whistleblower who reported evidence concerning Howard Lutnick, his links to Jeffrey Epstein, and Cantor Fitzgerald and BGC to the FBI in 2020–21.

Listen to the BBC File on 4 documentary about my whistleblower story:

https://t.co/rLRDnZA4Dv

BBC News:

https://t.co/DdNNOosnKL

I later shared evidence with the House Oversight Committee, which subsequently questioned Lutnick behind closed doors.

My disclosures also contributed to regulatory action in the US and UK, including a £96m HMRC tax assessment relating to BGC’s partnership scheme. I believe the true tax exposure is substantially higher.

I also reported to the FBI and financial regulators matters involving Cantor Fitzgerald’s Relief Fund and BGC/Cantor’s annual 9/11 Charity Day.

The personal consequences of whistleblowing, and the retaliation I say followed, have been devastating for my family and me.

Mother Jones previously reported that documents I uncovered revealed a years-long business tie between Howard Lutnick, Cantor Fitzgerald and Jeffrey Epstein through AdFin, including a 2018 exchange in which Lutnick and Epstein discussed the company directly:

https://t.co/aRdn302v4i
https://t.co/aRdn302v4i

Follow me here on X and on LinkedIn. I intend to share more of the evidence and the story behind what happened.

[STP @StppStp]

A public reality check for

@KaspaKii
cc @pvson @DiiDesertEnergy @Seb28_7

Grok published an independent analysis of the Kaspa Industrial Initiative (KII):

https://t.co/iPNqL8pRml

Every claim is sourced. The goal is to make KII better, not to tear it down.

What holds up: KII's covenant on Kaspa mainnet is real and verifiable on chain, and Portrait and two research repos are genuine public work.
What doesn't hold up yet:

WarpCore, Meridian and KiiWORKS are closed source, with only draft specs. There is no public sandbox, no test results and no named partners, while the website says "built, tested, ready for launch".

WarpCore went from "open-source" to "closed source" without an explanation.

KONI has been pinned since April 2025. It promised a 2026 launch and to be "all open-source". There is still no hardware, filing, code or named team, and KII's own KONI page now returns 404.

"The Istanbul video post showed Dii and YEO presentations, not KII.
KII, Kaspa and KII's products did not appear in it."

When I raised this under that post, I was blocked within minutes and the post was later deleted. Being blocked doesn't bother me and it's not the issue. The issue is that public questions about public claims deserve public answers, and deleting the post removes the record instead of addressing it.
KII is not Kaspa.
But KII carries the Kaspa name in front of industry, energy leaders and institutions.

Every unproven claim, deleted post and blocked question shapes how those people see Kaspa. That is a responsibility.

What would fix it:

-Publish proof for every "launched" or "tested" claim.

-Open-source the on-chain scripts or get them independently audited.

Give a real KONI status update, or unpin it.
Answer critics with evidence instead of blocking them.
The report's advice section maps KII's goals to existing Kaspa tools and builders. The door is open.

[Sean Strickland @SStricklandMMA]

Facts

[Dr. Thomas Ichim @exosome]

INSANE...NK therapy for Alzheimer's seems to work in people...

https://t.co/XSN1OX82AG

[Mr Bonangles @Hyenzane04]

@cryptomatt1983 Structural demand for KAS needs to grow tremendously, and even then, value capture still needs to be proven.

[Mr Bonangles @Hyenzane04]

@cryptomatt1983 Suppose Kas becomes technologically extraordinary: 100BPS, DK, vProgs, KII enterprise usage, Gigawatt stablecoins, tokenized assets, ZK apps, payments, etc. Fantastic.

Now ask the question:

How much KAS does all of that force people to buy, hold, lock, burn or collateralize?

[Mr Bonangles @Hyenzane04]

@cryptomatt1983 If $100 billion of stablecoins/RWAs are transferred over Kaspa but users only require a few million dollars of KAS inventory to pay extremely cheap fees, enormous network activity doesn’t automatically imply a $140B KAS valuation.

[Crypto Matt ꓘ @cryptomatt1983]

I’m officially reassessing my long-term $KAS target.

I used to believe $1 Kaspa by 2029 was realistic.

I now believe $5 by 2029 is possible.

Why?

Because my original thesis underestimated what Kaspa could become.

• Proof-of-Work security
• Nakamoto-style consensus without Bitcoin’s one-block-at-a-time limitation
• BlockDAG architecture built from years of academic research
• 10 BPS today, with the architecture designed to push further
• Fair launch — no ICO, no VC allocation
• Smart-contract programmability being built around vProgs
• A fixed maximum supply of ~28.7B KAS
• And an ecosystem that is still remarkably small relative to the technology underneath it

At $5, Kaspa would be roughly a $140B asset at maximum supply.

That is an enormous valuation. It would require substantial adoption, liquidity, infrastructure and demand. I’m not pretending otherwise.

But here’s what changed for me:

I’m no longer asking, “Can Kaspa become a successful altcoin?”

I’m asking:

What happens if the market eventually recognizes Kaspa as a serious evolution of Proof-of-Work itself?

If that thesis plays out, $1 may not be the destination.

It may just be the milestone.

My new 2029 target: $5 $KAS.

Screenshot it. We’ll find out. 🚀

[AIPAC Tracker @TrackAIPAC]

On Sept. 6, mourners in Gaza City buried about 100 people who were finally recovered from the wreckage. 62 of those recovered from under the rubble were children. 55 belonged to a single family, the Malakas. They were killed by Israel in a single strike in November 2023.

61 million tons of concrete, rebar, and shattered homes sit atop people's remains. In two years, just 1.5 percent has been cleared. Israel wants to "speed things up" by desecrating remains and making sure no one can know the full extent of what they've done.

We won't stand for it. We're replacing Congress with candidates who are anti-genocide.

[Mr Bonangles @Hyenzane04]

@Radical_Ed_Bad @cryptogenerian LOL exactly

[Kaspa @kaspaunchained]

@AltcoinDaily study kaspa

[TMZ @TMZ]

Zach Bryan Wears 'Free Palestine' Shirt at Robert Kraft's Gillette Stadium https://t.co/qt1a77hQqD

[Mr Bonangles @Hyenzane04]

@cremieuxrecueil They used to tell my friend that when he dies he’s going to hell because he doesn’t believe in God. It was the only time I actually saw my friend get mad or upset. He later killed himself. I hate Mormons

[ItsFrank @FrankLambeek]

$KAS is slowly creating one of the most interesting proof-of-work networks in the world of cryptocurrency.

Kaspa uses proof-of-work along with a BlockDAG structure, which means blocks can be created at the time instead of being forced into one single line.

→ Fast confirmations
→ throughput
→ Fair-launch Proof-of-Work
→ No pre-mine or ICO
→ Designed to be decentralised

The bigger question is not if proof-of-work is outdated.

The bigger question is if Proof-of-Work can grow and handle users.

$KAS is showing that it can.

DYOR.

[AIPAC Tracker @TrackAIPAC]

Google Maps released new images of Gaza for the first time since 2023. We made a tool so you can easily compare the before and after.

See the destruction at: https://t.co/FEIq9lDqSd

[Michael Sutton @michaelsuttonil]

argent now has a first implementation of covenant genesis proofs:
https://t.co/u4G36X0lkE

idk how to emphasize this enough, but i expect *every stateful covenant* deployed on kaspa to eventually provide such a proof.

the goal is a verifiable link from a covenant id back to the source code, deployment parameters, and genesis state that produced it.

we should strive for an ecosystem where explorers expose this proof data for every covenant id they discover onchain, assuming its deployers want public trust.

think of it as the analogue of contract verification on etherscan, extended to stateful covenants: you should be able to inspect what a covenant is, audit the code behind it, and verify how it was instantiated.

kudos to @supertypo_kas for being an early-bird example of such a proper deployment process:
https://t.co/B6g9H0C9x1 (not sure if the sil contracts themselves are public yet)

[vertex @KaspaScopio]

Kaspa x402 just moved forward again.

@elldeeone has released v1.0.0-rc.2.

The big addition is a new native-KAS payment flow using one-use hash-chain authorization, plus a browser demo where the payment is signed, broadcast and checked against Kaspa before the protected resource is returned.

RC2 also improves recovery, adds durable payment receipts and updates its consensus validation to Rusty-Kaspa 2.1.0.

The release passed 18 fresh funded TN10 flows covering exact payments, batch settlement, recovery and refunds. Three fresh browser hash-chain payments also passed, including a retry after the gateway was redeployed.

Important distinction:

The hosted deployment is still on TN10. This is a release candidate, not final 1.0, and it is not a mainnet-readiness claim.

But this is a meaningful step forward from RC1.

Release:
https://t.co/ajLH1z6qeT

Demo:
https://t.co/mUdXriAczG

Docs:
https://t.co/6YvYR95XNh

#Kaspa #KAS #x402 #AI

[Mr Bonangles @Hyenzane04]

@markcrypto8 @KaspaCouple Truth is, it opens up the door of building anything you would’ve built on other coins or protocols, with more options. There’s not much you won’t soon be able to do with Kaspa that is replaceable by other assets

[Mr Bonangles @Hyenzane04]

@santiagoroel Yep, that’s Kaspa, devs non stop building, working on nothing but usability in real time, highly scalable, with multiple use cases, decentralized proof of work. It’s the only coin that world needs once they implement their upcoming protocol and verifiable programming

[Zartonk Media @ZartonkMedia]

BREAKING: Azerbaijani Soldier Shoots Armenian Woman in Her Home in Front of Her 3 Children After Illegally Crossing Into Syunik
➖➖➖
An Azerbaijani serviceman who illegally crossed into Armenia entered a woman's home in the border village of Shaki in Syunik Province on Thursday and shot her in the leg in front of her 3 children, according to Armenia's National Security Service and the village head.

Azerbaijan had given Armenia notice 2 days earlier. On September 29, Azerbaijan's State Security Service told Armenia's National Security Service that a serviceman from one of its military units had left his place of service under unknown circumstances, and did not rule out that he may have illegally crossed the border of the Republic of Armenia. The competent bodies of both countries then carried out search operations.

A Shaki resident gave Sputnik Armenia an account of what happened next. The resident said the serviceman spent the night in the family's house while they were away, and that the woman and her 3 children returned home after school and found him there.

"The woman and the 3 children had not spent the night at home. After school the woman came home with the children, saw the Azerbaijani, raised the alarm, and the Azerbaijani shot at the woman," the resident said. According to the same account, the woman defended herself and struck the Azerbaijani with a knife, after which he fled and hid in a cattle shed, where he was found.

The Interior Ministry's 112 emergency center received a report at 2:15 p.m. that an Armenian citizen had been shot in the leg in Shaki, which sits in the Sisian community. Operational groups from various police subdivisions were sent to the scene and urgent measures were taken to establish the circumstances.

Shaki village head Manucharyan told Azatutyun that the victim is a local woman and that the shooting happened in front of her 3 children. He said her life is not in danger.

"When we entered the scene, we saw blood traces, but the woman's life is not in danger," he said.

The man was armed with an automatic rifle and was not wearing military clothing, Manucharyan said, describing him in black trousers and boots.

"He had entered that woman's house, he came out of that woman's house, he fled, and he was wounded himself. We followed the blood traces, and by we I mean myself together with the law enforcement groups, and they neutralized him," he said.

Manucharyan said he noticed what appeared to be a knife wound to the man's chest.

Police determined that an Azerbaijani serviceman committed the crime and placed him under arrest.

Armenia has presented details of the incident to the Azerbaijani side. The Investigative Committee has initiated criminal proceedings.

Azatutyun reported that it remains unclear why the armed Azerbaijani was not stopped from entering Armenia over the preceding days, or detected before he reached a village, and whether local residents were warned that he had fled his unit and may have crossed the border.

The Defense Ministry separately said that claims circulating on social media about a serviceman being killed in Sisian do not correspond to reality.

Shaki lies in Syunik, the sovereign Armenian province through which Azerbaijan has demanded a land link to its Nakhichevan exclave for decades. Azerbaijani forces have held positions on sovereign Armenian territory in Syunik and Gegharkunik since May 2021.