V0.5 ⏳Investing. Rebuilt on-chain.
British Virgin Islands
Joined March 2021
- Tweets2.8K
- Following624
- Followers47.2K
- Likes1.5K
Tradestrike retweeted
I partly agree with @vladtenev
The issue is whether people clearly understand what they’re actually buying, what rights come with it, who is making the claims and whether those claims can actually be verified
This whole debate has become far too binary. At one end you have @carlosdomingo championing native onchain issuance. At the other, Vlad arguing that issuer approval shouldn’t be needed where existing shareholder rights remain unchanged.
My foot is firmly in neither camp.
Yes native issuance may is the gold standard, the
North Star, but it isn’t the only model with value. A derivative or tokenised interest can still give people credible access to high-quality assets, provided the legal structure, backing, risks and limitations are made completely clear.
This is exactly why we built Proof of Integrity.
Cryptographically verifiable proof of
who made the claim, what evidence they committed to, which rules applied and whether a mint was authorised under those rules when it happened.
Tamper-evident history they can independently inspect instead of simply being asked to trust the issuer.
Tokenisation should fix the opacity of legacy markets, not bring it onchain.
🚨LATEST: obinhood CEO Vlad Tenev argues that issuer approval should not be required for tokenized stocks when the underlying shareholder rights remain unchanged.
Tenev says issuer approval should only be required if a tokenized product changes shareholder rights, replaces the official stock ledger or creates new obligations for the company.
“Shares in a public company are transferable personal property. Owners of freely transferable shares should generally be able to decide how they hold and use them.”
Robinhood says its Stock Tokens are separately issued instruments backed 1:1 by underlying shares, giving investors economic exposure without changing the issuer’s rights or ownership structure.
Tenev’s broader message: “Going onchain shouldn’t give the issuer a veto it never had offchain.”
Tradestrike retweeted
This is awesome
Our goal has never been complicated: build the app we would want to use ourselves, one that delivers what blockchain promised.
medium.com/@tradestrike/inve…
medium.com/@tradestrike/inve…
TradeStrike.
Why we believe the future of investing is on-chain and in self-custody.
Beta testing is underway!
Our team of community testers are hard at work ensuring we zap any bugs before public launch 👨🔧
Tradestrike retweeted
Be careful out there folks.
A similar exploit is also ongoing across BNB Chain as well as Ethereum.
A few actions you can take:
- Revoke any approvals from your wallets.
- Use a fresh hot wallet.
- Move high value holdings to cold storage.
Reminder: We advise all users still using a hot wallet created before May 2024 to consider moving funds to a freshly created one.
We’ve identified the root cause of this morning’s incident affecting 28 STRX holders.
Our technical team has confirmed that the affected wallets were compromised due to a legacy vulnerability in external libraries from several years ago.
All 28 wallets were created before May 2024 using these libraries, which had insufficient entropy.
As a precaution, we strongly recommend that any user still holding funds in a wallet created before May 2024 generate a new wallet and transfer their assets to it.
To be clear:
- The STRX token contract was not affected and remains secure.
- STRX liquidity pools were not affected and remain secure.
- StrikeX backend systems were not compromised.
- No wallets created after May 2024 were affected.
Our investigation into the 28 affected wallets is ongoing. We’ll share further updates as we confirm whether all were created in V1 of our app or through a third-party product and later imported.
Reminder: We advise all users still using a wallet created before May 2024 to consider moving funds to a freshly created StrikeX wallet.
We’ve identified the root cause of this morning’s incident affecting 28 STRX holders.
Our technical team has confirmed that the affected wallets were compromised due to a legacy vulnerability in external libraries from several years ago.
All 28 wallets were created before May 2024 using these libraries, which had insufficient entropy.
As a precaution, we strongly recommend that any user still holding funds in a wallet created before May 2024 generate a new wallet and transfer their assets to it.
To be clear:
- The STRX token contract was not affected and remains secure.
- STRX liquidity pools were not affected and remain secure.
- StrikeX backend systems were not compromised.
- No wallets created after May 2024 were affected.
Our investigation into the 28 affected wallets is ongoing. We’ll share further updates as we confirm whether all were created in V1 of our app or through a third-party product and later imported.
We’ve identified the root cause of this morning’s incident affecting 28 STRX holders.
Our technical team has confirmed that the affected wallets were compromised due to a legacy vulnerability in external libraries from several years ago.
All 28 wallets were created before May 2024 using these libraries, which had insufficient entropy.
As a precaution, we strongly recommend that any user still holding funds in a wallet created before May 2024 generate a new wallet and transfer their assets to it.
To be clear:
- The STRX token contract was not affected and remains secure.
- STRX liquidity pools were not affected and remain secure.
- StrikeX backend systems were not compromised.
- No wallets created after May 2024 were affected.
Our investigation into the 28 affected wallets is ongoing. We’ll share further updates as we confirm whether all were created in V1 of our app or through a third-party product and later imported.
This morning, a number of STRX holders (28 wallets) were affected by an on-chain exploit.
We are actively investigating and want to share what we know so far.
We can confirm this is NOT an exploit of the STRX smart contract and NOT an exploit of any STRX liquidity pool.
Our investigation is ongoing and we are working to establish the root cause. We will share a full update once our technical team has concluded their review.
We will never DM you first. We will never ask for your seed phrase, private key, or for you to connect your wallet to a recovery site. Any message claiming to be StrikeX support reaching out to help is a scam.
Planned maintenance
09 Apr 2026
06:00–10:30 GMT
Wallet services will be temporarily unavailable while we carry out scheduled upgrades.
Be sure to follow our parent company for all things tokenisation, infrastructure and business updates @StrikeX
This quoted post is unavailable.
Be aware if you are using Probit exchange to hold STRX tokens you must remove them before the 8th of December.
And remember, self-custody ftw 🔒
probit.com/en-us/hc/10000001…
Tradestrike retweeted
Strong H1 from CMC. StrikeX and tokenisation move centre stage as the third vertical. £300M commercial paper added. What a time to be building within the group!
financemagnates.com/forex/br…
Tradestrike retweeted
Proof of Integrity (PoI) is the cryptographic validation layer of the StrikeX tokenisation engine.
Excited to share more soon on the architecture behind what we’re building.
Proof > Trust
$STRX
Relying on third-party aggregators will soon be a thing of the past as we continue developing our in-house data solution to deliver accurate, liquidity-weighted, and trusted price feeds ⚡
@CoinMarketCap this shouldn’t be happening, STRX showing a -60% price drop because your global average gives equal weight to a dead CEX pair with zero liquidity.
This shouldn’t be overriding deep DEX markets, It distorts data across every app using your feed, time to switch to @coingecko?
Tradestrike retweeted
StrikeX, in Collaboration with CMC Markets and CapX, Completes First Tokenised Share Issue, Setting… blog.strikex.com/strikex-in-…
