Docushield

We will do everything in our power to hold KMC and CHIPS accountable.

@Chips_Finance is a scam.

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.

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.

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.

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

🚨 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.

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: nitter.gq/Kaddex_Official/status…

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

🚨 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.

𝙅𝙤𝙞𝙣𝙩 𝙨𝙩𝙖𝙩𝙚𝙢𝙚𝙣𝙩 𝙤𝙛 𝙆𝙖𝙙𝙙𝙚𝙭 𝙖𝙣𝙙 𝙆𝙖𝙙𝙚𝙣𝙖 𝙈𝙞𝙣𝙞𝙣𝙜 𝘾𝙡𝙪𝙗 (𝙆𝙈𝘾) 𝙤𝙣 𝙆𝙖𝙙𝙙𝙚𝙭 𝙥𝙧𝙤𝙫𝙞𝙙𝙞𝙣𝙜 𝙩𝙚𝙘𝙝𝙣𝙞𝙘𝙖𝙡 𝙖𝙣𝙙 𝙤𝙥𝙚𝙧𝙖𝙩𝙞𝙤𝙣𝙖𝙡 𝙖𝙨𝙨𝙞𝙨𝙩𝙖𝙣𝙘𝙚 𝙩𝙤 𝙆𝙈𝘾 Kaddex (@Kaddex_Official) specialises in building comprehensive technology and governance solutions for blockchain, web3, and DeFi, primarily focusing on Kadena. Kadena Mining Club (@KDAMiningClub) was a dynamic enterprise in the digital asset space committed to revolutionising the mining experience for the Kadena community. Kaddex believes in instilling trust and stability in the Kadena (@kadena_io) ecosystem and serves as a bedrock for making Kadena great again (MAGA). As part of that mission, Kaddex regularly acquires and assists projects that request it. For example, WizardsArena uses the Kaddex Kadena API. KMC has gone through some unfortunate events (see: nitter.gq/Janrya/status/18223525…), resulting in the project winding down and reducing operational expenses to maximise the remaining value whilst maintaining critical functionality, including the marketplace and NFT artwork. KMC's digital assets total over 80,000 objects and 130 GB in size. At their peak, hosting these assets cost the project several thousand dollars a month. After the announcement about the future of the KMC project, Kaddex approached the remaining management to see how Kaddex could lend its assistance. Kaddex's @MW_Tech1337 (MW) is a holder of KMC NFTs, and the project directly impacted him. Kaddex offered to host KMC's assets free of charge on its globally distributed network comprising servers in 250 locations and on its dedicated IPFS network. There are no security implications; KMC can always move these assets to another provider. Along with providing technical assistance, Kaddex is pursuing legal recourse against former KMC CEO Matthew Durnya. The remaining KMC team is not involved in this lawsuit but has assisted Kaddex. In the future, Kaddex looks forward to partnering with Chips and believes in focusing on the future of the Kadena ecosystem whilst learning and holding accountable the past. Stay tuned for the future launch of the $MW token, which will secure Kadena's future. Michael Williams Managing Director, Kaddex Global

🚨🚨🚨 WHY KADENA SHUT DOWN ECKO 🚨🚨🚨 We have the reason @Kadena_io is dumping @eckoDAO. They are now supporting @taralli_labs, owned by Jacquin A Mininger and Francesco Melpignano (@fmelp), through Astropoll, Inc. Both are former Kadena employees operating out of the EU. This is theft all over again. We believe Francesco knew of our use of the Taralli mark as he's done time and time again. @kadena_io is using this proxy company where they have full control over the outcome versus having a real team at @eckoDAO. Kaddex takeover 2.0. Kaddex will fight hard for your rights including launching a class action against @fmelp for his coordinated attacks against @eckoDAO. We will hold @taralli_labs and @kadena_io accountable for essentially pheonixing @eckoDAO. Francesco needs to be in jail! Don't allow @kadena_io to get away with this. They are literally stealing your money, dumping it on you, and running away, skirting regulations. $MW token will let us do just this: reinvigorate the Kadena ecosystem and hold bad actors, including the L1 itself accountable, even if it means forking the network and removing team tokens.

We’re so sad to hear about the news at @eckoDAO. Whilst we had our differences we respect many of the team. We’re committed to continuing to advance the Kadena ecosystem. We’ve made offers to several ecko staff members who will be joining Kaddex. We intend to relaunch @eckoWALLET as X-WALLET until a transition plan is made to determine what wallets remain in the ecosystem and ensure a clear and transparent process is available. Our nodes are plug and play. We’re also committed to hosting a mirror of the @eckoDEX front end so users are able to interact with the blockchain. More details to come. Let’s make Kadena great again.

We’re only relaunching the DEX front end for now so it’ll still rely upon the $KDX token. However, as @Thanos8912 has noted the DEX does require manual work for certain aspects. We’re not sure exactly how much. We will try to work with the @eckoDAO team to take over those manual processes. In short, yes $KDX token will be used for the time being. When we launch $MW token we will give some incentive for $KDX and $DOCU holders. Our goal is to build an interim solution to allow an orderly transition and off-ramp from $KDX to $MW token and try to compensate to some extent those investors who have been active in the ecosystem and funded projects like ecko who benefit us all. Let’s make @kadena_io great again and $MW token will allow us to make that happen.