@Musabyhani
iAccount based inUnited States!
About this account
- Account based in
- United States
- Connected via
- United States App Store
! X says this location may be affected by a proxy or VPN.
Account-level information from X, not a live location or the device used for a specific post.
Lead Developer and Moderator @secondfiapp
Joined April 2012
- Tweets156
- Following387
- Followers4.4K
- Likes10K
Pinned Tweet
We’re sorry for the inconvenience caused by the recent Cardano/Secondify app hack. If you were affected, please send me a DM, and I’ll assist you with the usual resolution process. nitter.cf/messages/compose?recip…
Captain ADIYAMAN🛡 retweeted
As per our previous post:
nitter.cf/secondfiapp/status/206…
We have identified the root cause and have since rolled out a patch for all unaffected wallets. This will allow us to resume normal operations soon.
-----
Regarding affected wallets, 4 distinct draining events occurred. 3 were executed by external threat actors, resulting in a loss of ~16m ADA across 374 addresses.
To prevent total loss during the active exploit, emergency rescue measures were triggered to secure the available ~129m ADA and continues to be routed to an independent, qualified third-party custodian, where they are held securely for the benefit of the affected wallet addresses.
An external accounting firm has been engaged for a special audit to independently verify those holdings.
We are working to facilitate the verification process so users can claim back their assets safely. Affected users should submit their claim at support.secondfi.io
We take this incident seriously and are working to ensure all assets are returned to affected users as soon as possible.
As stated, we have identified the root cause, it is at the address level. Please DO NOT RESTORE your recovery phrase into another Cardano wallet, this does not mitigate the security risk. The security risk occurs when an affected user signs a transaction.
Further explanation to follow.
To provide more clarity, we have identified the nature of the incident, it is at the address level. The security risk affects wallet users when a transaction is signed.
Therefore recovery to another platform or wallet does not mitigate the risk.
🚨 DO NOT restore your recovery phrase into a new Cardano wallet.
We have isolated the affected wallets and will post mitigation steps shortly.
Captain ADIYAMAN🛡 retweeted
To provide more clarity, we have identified the nature of the incident, it is at the address level. The security risk affects wallet users when a transaction is signed.
Therefore recovery to another platform or wallet does not mitigate the risk.
🚨 DO NOT restore your recovery phrase into a new Cardano wallet.
We have isolated the affected wallets and will post mitigation steps shortly.
There has been conflicting advice from different community members in an attempt to be helpful.
⚠️ DO NOT RESTORE your recovery phrase into a new Cardano wallet.
As advised, do nothing until official steps come from SecondFi. The only thing you should do is submit a ticket at support.secondfi.io.
We will never DM you first or ask for your recovery phrase.
Captain ADIYAMAN🛡 retweeted
There has been conflicting advice from different community members in an attempt to be helpful.
⚠️ DO NOT RESTORE your recovery phrase into a new Cardano wallet.
As advised, do nothing until official steps come from SecondFi. The only thing you should do is submit a ticket at support.secondfi.io.
We will never DM you first or ask for your recovery phrase.
Captain ADIYAMAN🛡 retweeted
🚨 SECURITY UPDATE: Root Cause & Blast Radius Confirmed
We have isolated the root cause of the recent security incident. The issue was confined to our native Cardano web wallet generation software.
Our team has completed an onchain analysis to determine the scope of impact, and we are now finalizing an independent technical review with a leading blockchain security firm to validate our findings.
Captain ADIYAMAN🛡 retweeted
By collaborating with these ecosystem leaders, we are monitoring exchange touchpoints, and minimizing the impact on other protocols.
Cardano stands together. We are grateful for the support of the ecosystem and will continue to provide updates as our investigation and recovery efforts progress.
Captain ADIYAMAN🛡 retweeted
⚠️ What You Need to Know Right Now:
While SecondFi is in maintenance, you will not be able to undertake transactions.
Beware of Scammers: We are seeing an immediate surge in fake "support" accounts and impersonators.
Official Channels Only: SecondFi team members will NEVER DM you first, ask for your seed phrase, or request fund transfers.
All official support is handled strictly through logged tickets at secondfi.io.
Thank you for your patience and we will provide regular updates as we make progress.
Captain ADIYAMAN🛡 retweeted
Self-custody puts you in control of your funds.
It also means the safety part is on you.
Worth running through the basics:
▪️ Your recovery phrase stays with you. Nobody needs it, including us. Anyone who asks for it is trying to drain you.
▪️ You approve every transaction yourself, so actually read it first. Wrong amount, or an address you don't recognize? Don't sign.
▪️ Onchain, there's no undo button. The few seconds you spend checking the address are the only protection you get.
Need help? One portal: secondfi.io. There is no support on X. Anyone in your replies or DMs offering to recover your funds is running a scam.
Captain ADIYAMAN🛡 retweeted
End of thread. Only trust secondfi.io
Captain ADIYAMAN🛡 retweeted
End of thread. Only trust secondfi.io
Captain ADIYAMAN🛡 retweeted
Moved from @YoroiWallet?
A few things work better now. 🟦
Your funds are exactly where you left them.
One wallet at a time, with your balance up front.
More in the knowledge base: kb.secondfi.io
Captain ADIYAMAN🛡 retweeted
Kaspa-NG has an active PR here to update it to be toccata ready. github.com/aspectron/kaspa-n…
Once its reviewed it will be pushed to the master branch. It is recommended to wait for the official release before using. Keep checking here for the update - github.com/aspectron/kaspa-n…
Captain ADIYAMAN🛡 retweeted
A tutorial was published by @KaspaSilver to run a Kaspa node, go public, and solo mine on Linux, Windows, or Mac. Check it out and run a Kaspa node today!
youtu.be/B7MZ7RE9UZQ?si=G0JW…
Captain ADIYAMAN🛡 retweeted
The hard fork is expected to have consensus all around therefore you do not need to do anything with your $KAS. Wallets typically connect to public Kaspa nodes which will be updating.
Captain ADIYAMAN🛡 retweeted
$KAS The Toccata Hard Fork is now live! Update your nodes well before June 30th so that you can remain in consensus!
github.com/kaspanet/rusty-ka…
Captain ADIYAMAN🛡 retweeted
Kaspa Toccata mainnet process update:
Today we plan to publish the v1.3.0 mainnet pre-release, without activation, for 1–2 days of broader network sanity testing.
Assuming everything looks good, the following release will be v2.0.0, with activation planned for June 30, 4 weeks from today
Captain ADIYAMAN🛡 retweeted
$KAS Toccata hardfork test on testnet-10 was a succuss. Onwards towards mainnet! Official date details coming soon!
Captain ADIYAMAN🛡 retweeted
$KAS is approaching closer to Toccata going live on mainnet. One final hardfork test is being done on testnet-10 happening today!
Testnet-10 source: github.com/kaspanet/rusty-ka…
CPU miner for testnet-10: github.com/kaspanet/cpuminer…
The Toccata hardfork stack is now ready, and we’re entering the final stage before mainnet activation: a full hardfork activation on Testnet-10. The scheduled activation point is: May 18, 2026, 16:00 UTC DAA Score: 467_579_632
Everyone is welcome to join and mine on testnet, so we can verify the transition works fine before mainnet activation.
I wrote detailed instructions for joining as a testnet miner (Link in reply)
Captain ADIYAMAN🛡 retweeted
Kaspa.org has been refreshed.
Kaspa has a lot going on, but the main site does not need to put it all at the front door. Its first job is simple: help someone arrive, understand what Kaspa is, and know where to go next.
The previous site accumulated more over time. Pages, explanations, resources, and audiences were added. This version starts smaller, so it can grow with Kaspa from here.
The refresh is not just visual. The wording, structure, and narrative direction all needed attention IMO.
The content traces back to @hashdag’s writing, simplified for a first read. Kaspa is already deep enough. The first read should not make people work harder than necessary.
There are many true ways to talk about Kaspa, but Kaspa.org cannot carry twenty narratives at once. For this version, the strongest one to unify around is real-time decentralisation.
Part of the refresh was also about making the builder path easier to follow. Kaspa.org gives people the overview of what exists, why it matters, and where to go next. Docs.kaspa.org gives builders the deeper material, with room for examples, detail, and ongoing improvement.
Docs.kaspa.org starts with @IzioDev's work and has the broader goal of bringing important Kaspa L1 builder documentation into one place.
Both repos are public. Pages will be added, wording will change, gaps will be filled, and the work can happen in the open.
Big shoutout to @kasmediadotcom for their support in helping bring this refresh together.
Have a look around. If you see something that can be better, please open an issue or PR.
Captain ADIYAMAN🛡 retweeted
Feature freeze is here for Toccata! This means that no further consensus rule changes will be made as preparations are being made for the Toccata hard fork.
Toccata is going to bring loads of features to Kaspa such as ZK proofs, Programmable UTXOs, and more!