Tech entrepreneur.
San Francsico, CA
Joined August 2023
- Tweets483
- Following146
- Followers231
- Likes107
Michael Williams retweeted
My Experience With @speedify and @alexgizis (the“Redundant Mode” Caused Outages, and Support Made It Worse by Cutting Me Off
This is my personal experience with Speedify (Connectify). I’m posting this publicly because what happened wasn’t just disappointing — it was reckless.
Why I bought it
I purchased Speedify for a router use case: bonding multiple internet links and, more importantly, redundancy/failover so that if one WAN link dropped or got unstable, traffic would continue on the other stable links.
Speedify markets exactly that promise: seamless failover, uninterrupted connectivity, “redundant mode,” etc.
What actually happened in real use
From the start, the product didn’t behave like “redundancy” at all.
Instead:
Redundant Mode did not provide flawless failover.
When one WAN link flapped, Speedify would drop the entire tunnel across all connections — including the connections that were still stable.
The result was full outages — the exact opposite of why you buy redundancy.
On top of that, performance degraded:
No meaningful “speed boost”
No “high efficiency bonding”
Increased instability that made real-time communications worse, not better
What support did (and why this is the part people should care about)
I opened a support ticket immediately and provided logs/details. Instead of focusing on a fix, the interaction quickly slid toward refund/cancellation rather than resolution.
Support also:
said they’d had no other reports of the issue on my router model and asked for logs/timestamps
asserted my links were “maxing out” at low upload speeds (which I disputed with comparative testing)
introduced licensing confusion (router licensing vs regular licenses), despite the fact I’d paid for a router-focused plan
So far: frustrating, but not unheard of.
Then came the truly unacceptable part.
The vendor-triggered outage
I explicitly told them not to cancel/refund because I was relying on the router subscription during an international trip / live situation, and I could not swap hardware mid‑event. I wanted them to fix the issue, not kill the service.
Despite that, Speedify processed refunds and expired/deactivated my plans anyway, including the router subscription (and even impacted another plan). I then received emails effectively saying this was a “follow up to your cancellation request” — except I did not make a cancellation request.
That refund/expiration wasn’t just a billing event — it instantly deactivated the service, which meant:
router authentication stopped working
connectivity dropped
systems went offline
I experienced major disruption and downtime at a critical time
In plain English: the product was already failing, and when I complained, support pulled the plug.
Why I’m warning others
In my view, the biggest risk with Speedify isn’t only performance — it’s that your connectivity can be remotely ended by the vendor, even while you’re actively using it, even after you’ve explicitly said “do not cancel,” and even when cancellation will obviously cause damage.
That’s not redundancy.
That’s vendor-controlled fragility.
If you’re considering Speedify for any critical use case (business continuity, travel, events, remote access), my advice is simple: test aggressively and assume your service can disappear instantly if a billing/refund action happens — even one you didn’t request.
My Experience With @speedify and @alexgizis (the“Redundant Mode” Caused Outages, and Support Made It Worse by Cutting Me Off
This is my personal experience with Speedify (Connectify). I’m posting this publicly because what happened wasn’t just disappointing — it was reckless.
Why I bought it
I purchased Speedify for a router use case: bonding multiple internet links and, more importantly, redundancy/failover so that if one WAN link dropped or got unstable, traffic would continue on the other stable links.
Speedify markets exactly that promise: seamless failover, uninterrupted connectivity, “redundant mode,” etc.
What actually happened in real use
From the start, the product didn’t behave like “redundancy” at all.
Instead:
Redundant Mode did not provide flawless failover.
When one WAN link flapped, Speedify would drop the entire tunnel across all connections — including the connections that were still stable.
The result was full outages — the exact opposite of why you buy redundancy.
On top of that, performance degraded:
No meaningful “speed boost”
No “high efficiency bonding”
Increased instability that made real-time communications worse, not better
What support did (and why this is the part people should care about)
I opened a support ticket immediately and provided logs/details. Instead of focusing on a fix, the interaction quickly slid toward refund/cancellation rather than resolution.
Support also:
said they’d had no other reports of the issue on my router model and asked for logs/timestamps
asserted my links were “maxing out” at low upload speeds (which I disputed with comparative testing)
introduced licensing confusion (router licensing vs regular licenses), despite the fact I’d paid for a router-focused plan
So far: frustrating, but not unheard of.
Then came the truly unacceptable part.
The vendor-triggered outage
I explicitly told them not to cancel/refund because I was relying on the router subscription during an international trip / live situation, and I could not swap hardware mid‑event. I wanted them to fix the issue, not kill the service.
Despite that, Speedify processed refunds and expired/deactivated my plans anyway, including the router subscription (and even impacted another plan). I then received emails effectively saying this was a “follow up to your cancellation request” — except I did not make a cancellation request.
That refund/expiration wasn’t just a billing event — it instantly deactivated the service, which meant:
router authentication stopped working
connectivity dropped
systems went offline
I experienced major disruption and downtime at a critical time
In plain English: the product was already failing, and when I complained, support pulled the plug.
Why I’m warning others
In my view, the biggest risk with Speedify isn’t only performance — it’s that your connectivity can be remotely ended by the vendor, even while you’re actively using it, even after you’ve explicitly said “do not cancel,” and even when cancellation will obviously cause damage.
That’s not redundancy.
That’s vendor-controlled fragility.
If you’re considering Speedify for any critical use case (business continuity, travel, events, remote access), my advice is simple: test aggressively and assume your service can disappear instantly if a billing/refund action happens — even one you didn’t request.
. @Kadena_IO spent $50 million in legal expenses fighting @Kaddex_Official instead of working collaboratively they finally shut down after a huge loss in the EU General Court. Incredible day to a Tier 1 blockchain that was once the sixth largest by market cap have to shut down.
Michael Williams 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.
Michael Williams 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.
Michael Williams 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!
Nicely done.
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
Michael Williams 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
I've asked our teams to discuss this with Kadena should they approach us to work collaboratively.
🚨 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.
Michael Williams 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.
Michael Williams 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: nitter.gq/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.
Michael Williams retweeted
Even legendary Pascal agrees with our assessment.
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…
I want to personally thank our Kaddex Security Operations Centre and Critical Incident Response Team for their excellent work on this!
🚨 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.
Michael Williams 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.
Glad that we’re able to assist!
𝙅𝙤𝙞𝙣𝙩 𝙨𝙩𝙖𝙩𝙚𝙢𝙚𝙣𝙩 𝙤𝙛 𝙆𝙖𝙙𝙙𝙚𝙭 𝙖𝙣𝙙 𝙆𝙖𝙙𝙚𝙣𝙖 𝙈𝙞𝙣𝙞𝙣𝙜 𝘾𝙡𝙪𝙗 (𝙆𝙈𝘾) 𝙤𝙣 𝙆𝙖𝙙𝙙𝙚𝙭 𝙥𝙧𝙤𝙫𝙞𝙙𝙞𝙣𝙜 𝙩𝙚𝙘𝙝𝙣𝙞𝙘𝙖𝙡 𝙖𝙣𝙙 𝙤𝙥𝙚𝙧𝙖𝙩𝙞𝙤𝙣𝙖𝙡 𝙖𝙨𝙨𝙞𝙨𝙩𝙖𝙣𝙘𝙚 𝙩𝙤 𝙆𝙈𝘾
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
Michael Williams retweeted
𝙅𝙤𝙞𝙣𝙩 𝙨𝙩𝙖𝙩𝙚𝙢𝙚𝙣𝙩 𝙤𝙛 𝙆𝙖𝙙𝙙𝙚𝙭 𝙖𝙣𝙙 𝙆𝙖𝙙𝙚𝙣𝙖 𝙈𝙞𝙣𝙞𝙣𝙜 𝘾𝙡𝙪𝙗 (𝙆𝙈𝘾) 𝙤𝙣 𝙆𝙖𝙙𝙙𝙚𝙭 𝙥𝙧𝙤𝙫𝙞𝙙𝙞𝙣𝙜 𝙩𝙚𝙘𝙝𝙣𝙞𝙘𝙖𝙡 𝙖𝙣𝙙 𝙤𝙥𝙚𝙧𝙖𝙩𝙞𝙤𝙣𝙖𝙡 𝙖𝙨𝙨𝙞𝙨𝙩𝙖𝙣𝙘𝙚 𝙩𝙤 𝙆𝙈𝘾
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
Kadena Mining Club NFTs "WILL NOT MINE AGAIN"
KMC releases lengthy statement regarding the state of the project.
What do we now know?
1. Former CEO, Matthew Durnya abandoned the project after failing to appropriately manage the project finances/assets.
2. The rest of the KMC team were unaware of the mismanagement until approximately 3 months ago and have since contributed their own money and time to work towards making things as right as possible for the community.
3. KMC NFTs will never mine again.
4. KMC Vial purchases (for increased hashrate) will not be fulfilled.
5. Pre-ordered mining machines that haven't been fulfilled will never be fulfilled as the funds for those pre-orders were used for other company expenses.
6. All KMC assets will be liquidated.
7. A DAO model is being created to give the community the power to decide the reimbursement model after that liquidation.
8. Hosted Machines that have been fulfilled will be shipped to their owners as soon as possible OR you may transfer your contract to Coastal Crypto for ongoing hosting. (Rack fee will be waived.)
9. The team has created a new project called Chips! (More details in future posts.)
Sad news for the Kadena Ecosystem and KMC community today.
Let me know your thoughts, good or bad, in the comments...
Michael Williams retweeted
🚨🚨🚨 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.
Hi @AdrianCardoso / @eckoDEX / @eckoDAO - where is the code for the eckoDAO stats service? (REACT_APP_KADDEX_STATS_API_URL=stage.swap.kaddex.com:5011)