Replying to @graftonsmith0 @Gensuki_
Transparency and assurance
Replying to @cryptic__Lab @Gensuki_
Because in the end, being audited isn't the same as being permanently secure.
So what will the evidence ultimately say about Gensuki, because web3 needs both questions answered with evidence and transparency before users pay the price again.
Replying to @cryptic__Lab @Gensuki_
And what happens when a researcher raises something unfounded, but the project still burns time and resources responding under public pressure?
And if genuine issues are confirmed, how will Gensuki respond?
Replying to @cryptic__Lab @Gensuki_
Are they actually exploitable? Were they already known or addressed?
The real questions aren't about tone or program names.
What happens when a concern gets raised, evidence gets submitted, and the project dismisses it, only for it to prove valid later?
Replying to @cryptic__Lab @Gensuki_
What happens when new security concerns still surface?
I'm not taking either side here because the actual findings matter more than the narrative.
The interesting part is what happens next.
Can the reported issues be reproduced?
Replying to @cryptic__Lab @Gensuki_
shouldn't that at least get serious technical attention?
And if the project has audits or good reasons to challenge the points, shouldn't these reasons be transparent enough for independent assesment?
Replying to @cryptic__Lab @Gensuki_
I'm not saying the project is vulnerable because someone flagged stuff from public info. But when someone reviews only what's already public, avoids anything intrusive, documents concerns, submits privately, and still offers authorized follow-up,
with damage in the hundreds of millions.
Thatโs what got me interested in this @Gensuki_ swap.
I have no personal knowledge of the researcher, and I do not claim that their findings are automatically right.
Security concerns in Web3 don't get measured by how many followers the person raising them has.
The Bitget breach was a prove of that. Questions were already circulating before September and the investigation later confirmed a third-party vulnerability was the entry point,....
Hi @Gensuki_ team,
I know we started off on a wrong foot but lemme set things straight here
I came across your Project through a friend who had some security concerns about it and asked me to peep so I decided to take a look myself
I started with what anyone could see publicly....the website, exposed infra, public repos, configs, on-chain information and all of those
There were nothing intrusive too lemme mention, no wallet connected, no transaction signed, no account created
I still noticed a few things worth flagging and i reached out to your team through @Hopeepik . He connected me with your CTO and @pa_cem23 Founder in a discord group and I initially tried to move the conversation toward a proper engagement through our Founding50 program with @ancientechLABS rather than simply dropping a full report there
There was some back and forth around the concerns I raised, including questions about whether there was enough evidence behind them and references to previous audits the project had undergone
Now I understand that part....
More reason I decided to complete the research and send the findings directly
The report is now with @Hopeepik on the @Gensuki_ team
I'm not saying I'm going to publish any findings here please or turn this into a public call-out. Naaa I'm just setting things straight especially for reference purposes
They have the information now and I genuinely hope the team reviews everything and addresses whatever needs attention
I'd still be happy to work with the team properly and take the research further with authorized access
Like the CTO asked me "what are you proposing?"
What we wanna help close in your project is in our Founding50 structure
Yeaaa
Have a wonderful Friday
Cryptic_Lab๐๐๏ธ๐ retweeted
Hi @Gensuki_ team,
I know we started off on a wrong foot but lemme set things straight here
I came across your Project through a friend who had some security concerns about it and asked me to peep so I decided to take a look myself
I started with what anyone could see publicly....the website, exposed infra, public repos, configs, on-chain information and all of those
There were nothing intrusive too lemme mention, no wallet connected, no transaction signed, no account created
I still noticed a few things worth flagging and i reached out to your team through @Hopeepik . He connected me with your CTO and @pa_cem23 Founder in a discord group and I initially tried to move the conversation toward a proper engagement through our Founding50 program with @ancientechLABS rather than simply dropping a full report there
There was some back and forth around the concerns I raised, including questions about whether there was enough evidence behind them and references to previous audits the project had undergone
Now I understand that part....
More reason I decided to complete the research and send the findings directly
The report is now with @Hopeepik on the @Gensuki_ team
I'm not saying I'm going to publish any findings here please or turn this into a public call-out. Naaa I'm just setting things straight especially for reference purposes
They have the information now and I genuinely hope the team reviews everything and addresses whatever needs attention
I'd still be happy to work with the team properly and take the research further with authorized access
Like the CTO asked me "what are you proposing?"
What we wanna help close in your project is in our Founding50 structure
Yeaaa
Have a wonderful Friday
This is exactly why I think $QOR deserves serious attention before the market fully discovers it ๐๐ฅ
@QoreChain didnโt wait for TGE to start building. The mainnet is already live, the technology is verifiable on-chain, the code is open-source and its post-quantum infrastructure has been running since day one.
And thereโs another important piece: QoreX
QoreChainโs own non-custodial wallet brings its quantum-safe infrastructure directly to users, with QOR transfers protected by post-quantum signatures while keeping the experience simple.
So weโre not looking at just another token launch here.
A working Layer 1 โ
Post-quantum security โ
Triple-VM infrastructure โ
QoreX wallet โ
$QOR entering the market โ
With the listing only hours away, I think this is one of those projects you donโt want to discover too late.
Do your research, watch $QOR closely and keep @QoreChain on your radar today ๐
#QoreChain #QOR #QoreX #MEXC #Layer1 #Web3
In under four hours QOR lists. Before it does, here is how to check us instead of believing us.
Block time, measured this morning across the last 100,012 blocks: 2.33 seconds, with single block deterministic finality. Our own materials have been quoting 5 seconds, because that is the configured commit timeout. The chain is faster than our marketing.
Every transaction on the native lane requires an ML-DSA-87 signature. No classical fallback. That has been true since block one, 74 days ago.
The first transaction secured end to end by the full standardised NIST post-quantum stack:
4E49D57F86FEC8851CDC34811B4C80FDB24F4C253ABE15D25C05B7A27F2B7F1F
Validators, staking parameters and every balance are queryable right now at api.qore.host. Blocks and transactions at explore.qore.network. The post-quantum library is published on npm, PyPI, Maven, Go modules and crates.io. The code is Apache-2.0.
We shipped all of it before asking the market for anything. Argue with the chain, not with us.

ALT QoreChain card titled Measured, not claimed. Mainnet values queried live on 20 August 2026: block time 2.33 seconds across the last 100,012 blocks, finality 1 block deterministic BFT, native lane signature ML-DSA-87 under FIPS 204 security category 5, classical fallback none, enforced since block one. Footer reads api.qore.host, verify every line yourself.
Replying to @QoreChain
So excited for the outcome of this....LFG๐ฅ๐ฅ
Cryptic_Lab๐๐๏ธ๐ retweeted
Before tomorrow:
1. Install QoreX
2. Bookmark explore.qore.network
3. Follow this account and nothing else claiming to be us
Several fake QOR tokens appeared today on DEXs across multiple chains. None of them are ours. QOR is native to QoreChain - we have never deployed a QOR contract on Base, Ethereum, BNB, Solana or any other chain, and any token you find there under our name or our logo is fake.
The real QOR trades in one place: MEXC, starting tomorrow, 20 August, 13:00 UTC.
QoreX is free and non-custodial:
Chrome โ chromewebstore.google.com/deโฆ
Firefox โ addons.mozilla.org/firefox/aโฆ
macOS โ apps.apple.com/us/app/qorex-โฆ
Android โ play.google.com/store/apps/dโฆ
iOS, TestFlight open beta โ testflight.apple.com/join/Xaโฆ
We will never DM you first. Nobody from QoreChain will ever ask for your seed phrase. Every account in your mentions tomorrow offering you something is a fake account.
Tomorrow is a big day for @QoreChain ๐
The $QOR MEXC Kickstarter is already LIVE with a 3,000,000 QOR reward pool, while trading officially begins tomorrow, August 20 at 13:00 UTC.
But QoreChain is much more than just another new token listing.
Itโs an already-built Layer 1 focused on post-quantum security and AI-native infrastructure, with EVM, CosmWasm and SVM brought together within the same ecosystem.
What caught my attention most is simple: they built the technology first, and the token is coming to the market after.
With the Kickstarter now live and the MEXC listing just hours away, $QOR is entering an important new chapter.
Definitely one Iโd recommend researching and keeping on the radar ๐
Follow @QoreChain for the latest updates.
#QoreChain #QOR #MEXC #Layer1 #Web3
Before tomorrow:
1. Install QoreX
2. Bookmark explore.qore.network
3. Follow this account and nothing else claiming to be us
Several fake QOR tokens appeared today on DEXs across multiple chains. None of them are ours. QOR is native to QoreChain - we have never deployed a QOR contract on Base, Ethereum, BNB, Solana or any other chain, and any token you find there under our name or our logo is fake.
The real QOR trades in one place: MEXC, starting tomorrow, 20 August, 13:00 UTC.
QoreX is free and non-custodial:
Chrome โ chromewebstore.google.com/deโฆ
Firefox โ addons.mozilla.org/firefox/aโฆ
macOS โ apps.apple.com/us/app/qorex-โฆ
Android โ play.google.com/store/apps/dโฆ
iOS, TestFlight open beta โ testflight.apple.com/join/Xaโฆ
We will never DM you first. Nobody from QoreChain will ever ask for your seed phrase. Every account in your mentions tomorrow offering you something is a fake account.
Cryptic_Lab๐๐๏ธ๐ retweeted
A Hero becomes much more interesting when it has a place in the world.
Instead of simply owning artwork, @DungeonSaga aims to give every collectible a connection to Kronos, its lore and its ongoing story.
That's the kind of direction I'd like to see more projects take.
Replying to @dungeonsaga
Getting the new series started ๐ฅ๐ฅ
Cryptic_Lab๐๐๏ธ๐ retweeted
๐ค What Happens When AI Agents Need to Pay Each Other?
The next frontier isnโt just AI โ itโs autonomous economies.
๐
June 18, 3 PM UTC
๐ Set reminder: xitter.cf/i/spaces/1kJzDDEZVmwKvโฆ
Featuring:
โข Dafu โ Chief Evangelist @clawchatglobal
โข Bruce Liu โ Founder @op_catlayer
โข Vlada โ Ecosystem Head @NoosProtocol
โข Amar โ Co-founder @dungeonsaga
โข Eric Chiew โ BD Lead @termix_ai
โข Konsole โ AI Engineer
If AI agents can think, act, and earnโฆ
Who pays them โ and how? ๐
what's the first thing you'd want to do? ๐
๐ฅ Grab your Beta invite now:
1๏ธโฃ Follow @clawchatglobal & @op_catlayer
2๏ธโฃ Join Telegram: t.me/opcat_layer
3๏ธโฃ Post in the Early Access topic: โJoin ClawChat Betaโ
#ClawChat #OPCATLayer #Bitcoin #SocialFi
The first BTC-native social protocol on @op_catlayer โ E2E encrypted, Agent-ready, every interaction becomes an on-chain asset.
For the first time, "identity" in Web3 isn't just a buzzword.
If social data truly belonged to you,....
On @clawchatglobal: you're an on-chain identity.
Wallet = your name. Wallet = your chat key. Wallet = your interaction history. Wallet = your level in the system. Everything on-chain, everything portable, everything yours.
No phone number. No email. No company to trust.









