Your life - secured on the Blockchain. Full proof document vaults for the important and irreplaceable. Running on #Flux
SoCal, USA
Joined March 2022
- Tweets1.6K
- Following544
- Followers3.6K
- Likes2.8K
Pinned Tweet
Wow! @kadena_io Francesco Melpignano/ @fmelp are rekt. So embarrassing that they lied mislead investors and caused massive losses to $KDX holders. Glad the truth is coming out!
We finally have extensive and concrete proof of @kadena_io and @fmelp's involvement in the early days of Fakedex (Kaddex US Holdings, Inc. [KUSH]).
As previously reported, Francesco exercised significant control over KUSH, met and directed employees, and was paid hundreds of thousands for his involvement.
Through Francesco and Bertrand, Kadena provided day-to-day oversight, further funding, and direction to Fakedex. The very invoice for creating Fakedex/KUSH was sent to Francesco and Kadena (screenshot highlighted below).
We have tens of thousands of emails, voice messages, recordings of calls, chat transcripts, and more documenting this serious misconduct and flat-out lies to the Kadena community.
We will finally file a lawsuit against Kadena and Francesco, Bertrand, and others for participating in one of the largest frauds ever committed in the Kadena community. @fmelp is a liar and a fraud. He deserves to be in jail. The lies Kadena, Francesco, and others have sold to the Kadena community are unbelievable.
Note that this does not reflect on the DAO run separately - we respect @eckoDAO and their staff.
Docushield retweeted
As expected. Scammers will scam again. Incredible work by the @Kaddex_Official team to shut them down.
Docushield retweeted
In the coming months after our lawsuit is launched we will provide as much evidence as legally possible showing the @Chips_Finance founders, executives, and staff knowledge or flat out involvement in the @KDAMiningClub fraud.
Docushield retweeted
Shut these guys down. I love how Kadena continually gives grant to scam companies. First Fakedex (KUSH), then Kadena Mining Club, and now CHIPS.
All - We are happy to announce that we will be pursuing legal action against @Chips_KDA along with any of its employees connected with KMC. We believe CHIPS is a phoenixing operation and that the executive-level employees who essentially acted with fiduciary responsibilities knew or should have known KMC's defects. We assert the wind-down operation of KMC is illegal under US securities laws and was not done under the supervision of a proper Trustee in a bankruptcy court.
We urged CHIPS staff to do the right thing by appointing Kaddex as an independent auditor but they refused. We will continue to make Kadena great again. I believe this message will be deleted but will be reposted on our X account. We will provide details for affected individuals to join the class and recover their KMC losses from CHIPS which is essentially an incognito version of KMC.
Seemed suss that KMC shuts down but CHIPS keeps control then directs all the capital to their own project and makes holders take loss!?
All - We are happy to announce that we will be pursuing legal action against @Chips_KDA along with any of its employees connected with KMC. We believe CHIPS is a phoenixing operation and that the executive-level employees who essentially acted with fiduciary responsibilities knew or should have known KMC's defects. We assert the wind-down operation of KMC is illegal under US securities laws and was not done under the supervision of a proper Trustee in a bankruptcy court.
We urged CHIPS staff to do the right thing by appointing Kaddex as an independent auditor but they refused. We will continue to make Kadena great again. I believe this message will be deleted but will be reposted on our X account. We will provide details for affected individuals to join the class and recover their KMC losses from CHIPS which is essentially an incognito version of KMC.
Docushield retweeted
All - We are happy to announce that we will be pursuing legal action against @Chips_KDA along with any of its employees connected with KMC. We believe CHIPS is a phoenixing operation and that the executive-level employees who essentially acted with fiduciary responsibilities knew or should have known KMC's defects. We assert the wind-down operation of KMC is illegal under US securities laws and was not done under the supervision of a proper Trustee in a bankruptcy court.
We urged CHIPS staff to do the right thing by appointing Kaddex as an independent auditor but they refused. We will continue to make Kadena great again. I believe this message will be deleted but will be reposted on our X account. We will provide details for affected individuals to join the class and recover their KMC losses from CHIPS which is essentially an incognito version of KMC.
Docushield retweeted
We finally have extensive and concrete proof of @kadena_io and @fmelp's involvement in the early days of Fakedex (Kaddex US Holdings, Inc. [KUSH]).
As previously reported, Francesco exercised significant control over KUSH, met and directed employees, and was paid hundreds of thousands for his involvement.
Through Francesco and Bertrand, Kadena provided day-to-day oversight, further funding, and direction to Fakedex. The very invoice for creating Fakedex/KUSH was sent to Francesco and Kadena (screenshot highlighted below).
We have tens of thousands of emails, voice messages, recordings of calls, chat transcripts, and more documenting this serious misconduct and flat-out lies to the Kadena community.
We will finally file a lawsuit against Kadena and Francesco, Bertrand, and others for participating in one of the largest frauds ever committed in the Kadena community. @fmelp is a liar and a fraud. He deserves to be in jail. The lies Kadena, Francesco, and others have sold to the Kadena community are unbelievable.
Note that this does not reflect on the DAO run separately - we respect @eckoDAO and their staff.
Docushield retweeted
I am happy to announce I’ve begun full time employment at @Kaddex_Official as their social media coordinator working directly for Frog.
We’re going to make @kadena_io great again!
Kaddex continues to innovate building top tier solutions for blockchain applications!
The Kadena Mempool is a temporary storage area for transactions waiting to be confirmed and added to a block. Kaddex has launched an easy-to-use mempool viewer that allows users to peer into these transactions. A transaction’s presence in a mempool does notn necessarily mean it will succeed or even be included in a block.
Kaddex’s data is nearly real-time. We update our mempool snapshot every three (3) seconds and refresh the viewer every ten (10) seconds after the page loads. The snapshot is available as a JSON file or viewable in the interactive table below.
kaddex.xyz/about/kadena/memp…
CC: @kadena_io #Kadena #MakeKadenaGreatAgain
Docushield retweeted
The Kadena Mempool is a temporary storage area for transactions waiting to be confirmed and added to a block. Kaddex has launched an easy-to-use mempool viewer that allows users to peer into these transactions. A transaction’s presence in a mempool does notn necessarily mean it will succeed or even be included in a block.
Kaddex’s data is nearly real-time. We update our mempool snapshot every three (3) seconds and refresh the viewer every ten (10) seconds after the page loads. The snapshot is available as a JSON file or viewable in the interactive table below.
kaddex.xyz/about/kadena/memp…
CC: @kadena_io #Kadena #MakeKadenaGreatAgain
If Kadena doesn’t publicly reach out and engage we will certainly remember this point forward! This is their chance to make things right!
🚨 KADDEX DISCOVERS SEVERAL FURTHER MAJOR VULNERABILITIES IN KADENA BLOCKCHAIN🚨
Summary:
Kaddex discovered several more attack vectors that are far more dangerous than the ones exploited today. We encourage @kadena_io to reach out to our team to discuss remediation.
Using these vectors could allow an attacker to control the entire blockchain through a 51% attack and cause massive losses to token holders.
Details:
Kaddex provides trust and stability in the Kadena ecosystem, serving as the bedrock of the blockchain.
As part of our continued efforts in security and providing a hardened chainweb-node instance, our engineers took an expedited approach to analyse all endpoints of chainweb-node to prevent other attack vectors similar to today.
In doing so, Kaddex security engineers have discovered several significant vulnerabilities in the Kadena blockchain, allowing for a far more sophisticated DDoS attack than currently occurring. A 51% attack is possible by exploiting these vulnerabilities coordinatedly. Extensive loss to token holders might occur, primarily if an attacker identifies and excludes exchanges' nodes.
We encourage the Kadena team to contact us to discuss this vulnerability. The Kaddex team was the first to identify, report, block, and patch the issue today. Had today's attacker been more sophisticated, they could have orchestrated a 51% attack, as has been possible multiple times on the Kadena network.
We thank our Kaddex Security Operations Centre (KSOC), Kaddex Critical Incident Team (KCRIT), and security and software engineers for their excellent work.
We have already patched these vulnerabilities in our hardened chainweb-node version and deployed further web application firewall rules to prevent similar attacks.
Docushield retweeted
🚨 KADDEX DISCOVERS SEVERAL FURTHER MAJOR VULNERABILITIES IN KADENA BLOCKCHAIN🚨
Summary:
Kaddex discovered several more attack vectors that are far more dangerous than the ones exploited today. We encourage @kadena_io to reach out to our team to discuss remediation.
Using these vectors could allow an attacker to control the entire blockchain through a 51% attack and cause massive losses to token holders.
Details:
Kaddex provides trust and stability in the Kadena ecosystem, serving as the bedrock of the blockchain.
As part of our continued efforts in security and providing a hardened chainweb-node instance, our engineers took an expedited approach to analyse all endpoints of chainweb-node to prevent other attack vectors similar to today.
In doing so, Kaddex security engineers have discovered several significant vulnerabilities in the Kadena blockchain, allowing for a far more sophisticated DDoS attack than currently occurring. A 51% attack is possible by exploiting these vulnerabilities coordinatedly. Extensive loss to token holders might occur, primarily if an attacker identifies and excludes exchanges' nodes.
We encourage the Kadena team to contact us to discuss this vulnerability. The Kaddex team was the first to identify, report, block, and patch the issue today. Had today's attacker been more sophisticated, they could have orchestrated a 51% attack, as has been possible multiple times on the Kadena network.
We thank our Kaddex Security Operations Centre (KSOC), Kaddex Critical Incident Team (KCRIT), and security and software engineers for their excellent work.
We have already patched these vulnerabilities in our hardened chainweb-node version and deployed further web application firewall rules to prevent similar attacks.
💯 a DDoS.
Well, @_wjmartino_ (CEO/founder of @kadena_io) is an idiot. He claims there is no evidence that it's a DDoS except all our metrics, and CloudFlare clearly shows that it's a DDoS holding its network offline. There is no "evidence" because Kadena is so dumb that they run their p2p nodes directly interacting with the internet, so there is no intelligence and logging to provide insight.
At Kaddex, we have multiple layers of security and telemetry. We can see it's a DDoS with over 7 million requests to p2p endpoints in a minute. Their nodes won't go back online is that the DDoS is continuing... So, whenever they turn their nodes back on, they get overwhelmed and run out of memory/CPU.
It is so embarrassing that Kadena cannot fix something despite us telling them about the issue. It should be a five-minute fix. Instead, they lie to the community, misleading them, stating there are no issues and everything is fine.
The only reason some nodes are not offline right now is they either restrict the nodes they interact with or the attacker is not including them in their round-robin list.
See more: xitter.cf/Kaddex_Official/status…
Docushield retweeted
Well, @_wjmartino_ (CEO/founder of @kadena_io) is an idiot. He claims there is no evidence that it's a DDoS except all our metrics, and CloudFlare clearly shows that it's a DDoS holding its network offline. There is no "evidence" because Kadena is so dumb that they run their p2p nodes directly interacting with the internet, so there is no intelligence and logging to provide insight.
At Kaddex, we have multiple layers of security and telemetry. We can see it's a DDoS with over 7 million requests to p2p endpoints in a minute. Their nodes won't go back online is that the DDoS is continuing... So, whenever they turn their nodes back on, they get overwhelmed and run out of memory/CPU.
It is so embarrassing that Kadena cannot fix something despite us telling them about the issue. It should be a five-minute fix. Instead, they lie to the community, misleading them, stating there are no issues and everything is fine.
The only reason some nodes are not offline right now is they either restrict the nodes they interact with or the attacker is not including them in their round-robin list.
See more: xitter.cf/Kaddex_Official/status…
🚨 KADENA NETWORK UNDER ATTACK, KADDEX IDENTIFIES & PATCHES ISSUE - STATEMENT🚨
Summary:
On 25 August 2024, at approximately 01h00 UTC, the Kaddex Security Operations Centre (SOC) noticed a large-scale coordinated attack against the @kadena_io network that exhausted resources on Kadena nodes. Specifically, inbound HTTP requests exceeded 42x normal levels.
Should you wish to use Kaddex's nodes and API, they are available at api.kda.kaddex.xyz, which is a drop-in for api.chainweb.com or estats.chainweb.com. We have better security and uptime than Kadena, who seems oblivious and lazy at correcting issues.
Details:
At 02h00, @MW_Tech1337 activated the Kaddex Critical Incident Response Team (KCIRT).
KCIRT worked closely with the SOC and identified the attacker abusing a batch process on the Kadena node `/chainweb/0.0/mainnet01/chain/[chain_id]/payload/batch`. Should you wish to block the attacker, deploy rate limits or other protection on the endpoint above with a wildcard for [chain_id].
Whilst deploying firewall rules to our global network of nodes to block the attack, our developers began patching the issue in our forked version of chainweb-node.
This issue has occurred before, and we identified the problem with @kadena_io; however, they did not give us any credit for identifying and patching it.
Despite what Kadena states, their network regularly has outages due to poor coding and the inability to properly secure their infrastructure. Moreover, Kadena refuses to engage with other entities and hides their issues from the public.
The launch of $MW token is the only way to hold Kadena accountable and to make Kadena Great Again (MKGA). We intend to force Kadena to be accountable to the community or to fork their network entirely and build it right, listening to the community and implementing their feedback.
Please retweet and forward this to Kadena, as they blocked us and, without our insight, would probably let the network stay down for days.
Docushield retweeted
Our nodes, API, and block explorer remain online and ready for use.
Kadena claims there are no issues, and block production has not stopped. This is only because Poolflare and Kaddex are keeping the network online.
API: api.kda.kaddex.xyz
Explorer: explorer.kda.kaddex.xyz
Kaddex is the future! Go $MW!
🚨 KADENA NETWORK UNDER ATTACK, KADDEX IDENTIFIES & PATCHES ISSUE - STATEMENT🚨
Summary:
On 25 August 2024, at approximately 01h00 UTC, the Kaddex Security Operations Centre (SOC) noticed a large-scale coordinated attack against the @kadena_io network that exhausted resources on Kadena nodes. Specifically, inbound HTTP requests exceeded 42x normal levels.
Should you wish to use Kaddex's nodes and API, they are available at api.kda.kaddex.xyz, which is a drop-in for api.chainweb.com or estats.chainweb.com. We have better security and uptime than Kadena, who seems oblivious and lazy at correcting issues.
Details:
At 02h00, @MW_Tech1337 activated the Kaddex Critical Incident Response Team (KCIRT).
KCIRT worked closely with the SOC and identified the attacker abusing a batch process on the Kadena node `/chainweb/0.0/mainnet01/chain/[chain_id]/payload/batch`. Should you wish to block the attacker, deploy rate limits or other protection on the endpoint above with a wildcard for [chain_id].
Whilst deploying firewall rules to our global network of nodes to block the attack, our developers began patching the issue in our forked version of chainweb-node.
This issue has occurred before, and we identified the problem with @kadena_io; however, they did not give us any credit for identifying and patching it.
Despite what Kadena states, their network regularly has outages due to poor coding and the inability to properly secure their infrastructure. Moreover, Kadena refuses to engage with other entities and hides their issues from the public.
The launch of $MW token is the only way to hold Kadena accountable and to make Kadena Great Again (MKGA). We intend to force Kadena to be accountable to the community or to fork their network entirely and build it right, listening to the community and implementing their feedback.
Please retweet and forward this to Kadena, as they blocked us and, without our insight, would probably let the network stay down for days.
Docushield retweeted
🚨 KADENA NETWORK UNDER ATTACK, KADDEX IDENTIFIES & PATCHES ISSUE - STATEMENT🚨
Summary:
On 25 August 2024, at approximately 01h00 UTC, the Kaddex Security Operations Centre (SOC) noticed a large-scale coordinated attack against the @kadena_io network that exhausted resources on Kadena nodes. Specifically, inbound HTTP requests exceeded 42x normal levels.
Should you wish to use Kaddex's nodes and API, they are available at api.kda.kaddex.xyz, which is a drop-in for api.chainweb.com or estats.chainweb.com. We have better security and uptime than Kadena, who seems oblivious and lazy at correcting issues.
Details:
At 02h00, @MW_Tech1337 activated the Kaddex Critical Incident Response Team (KCIRT).
KCIRT worked closely with the SOC and identified the attacker abusing a batch process on the Kadena node `/chainweb/0.0/mainnet01/chain/[chain_id]/payload/batch`. Should you wish to block the attacker, deploy rate limits or other protection on the endpoint above with a wildcard for [chain_id].
Whilst deploying firewall rules to our global network of nodes to block the attack, our developers began patching the issue in our forked version of chainweb-node.
This issue has occurred before, and we identified the problem with @kadena_io; however, they did not give us any credit for identifying and patching it.
Despite what Kadena states, their network regularly has outages due to poor coding and the inability to properly secure their infrastructure. Moreover, Kadena refuses to engage with other entities and hides their issues from the public.
The launch of $MW token is the only way to hold Kadena accountable and to make Kadena Great Again (MKGA). We intend to force Kadena to be accountable to the community or to fork their network entirely and build it right, listening to the community and implementing their feedback.
Please retweet and forward this to Kadena, as they blocked us and, without our insight, would probably let the network stay down for days.