Urgent: Transfer Control of the Motoko Mechs Canister to the Motoko DAO – Honoring the Agreement with DFINITY Leadership

Hello DFINITY community,

I’m posting today to highlight a pressing issue that affects not just the Motoko NFT collections but the integrity and perception of the entire Internet Computer ecosystem. As many of you know, the Motoko Mechs collection an official blue-chip NFT series executive produced by DFINITY’s Andrew Tang in collaboration with artist Alex Wu was created in 2021 to celebrate the Internet Computer’s mainnet launch and Supernova milestone. This collection represents a flagship piece of DFINITY’s history, symbolizing innovation, community, and the early achievements of the protocol.

However, despite a longstanding agreement with DFINITY leadership, control of the Mechs canister (ID: r7g4r-piaaa-aaaak-acovq-cai) has not been transferred to the Motoko DAO, which holds the IP rights to the Motoko brand and is the designated custodian for all official Motoko collections (Ghosts, Mechs, and Sentinels). This agreement was confirmed publicly, including in discussions on this forum (e.g., threads like “Taking Motoko Sentinels Back” and “Upcoming SNS DAO for $MOTOKO”), where it’s clear that DFINITY intended for the DAO to manage these assets, including royalties, canisters, and ongoing development.

Bob Bodily, who currently holds control over the canister, was instructed long ago to complete this transfer. Instead, the canister has been effectively abandoned: it has run out of cycles, leading to 503 Service Unavailable errors when attempting to access or display the assets. This means holders can’t view their Mechs, and the collection is unusable akin to those infamous IPFS-hosted NFTs where someone forgot to pay the AWS bill. It’s a shameful state for an official DFINITY project, and it disrespects everyone who contributed to the 2021 launch, the artists involved, and the community that has supported ICP from the beginning.

To make matters worse, this neglect comes at a time when the community is actively building on the Motoko legacy. I’m currently developing Motoko Megz – a community-driven tribute to four years of DFINITY’s accomplishments, featuring 2,025 hand-designed 3D gaming assets. I had planned to showcase the original Mechs alongside Megz to honor the evolution of the brand, but that’s impossible with the canister offline. Details on Megz can be found here: X Post on Motoko Megz Launch and Follow-up on Display Issues. (this is not a shill for my collection, I am just deeply frustrated)

This isn’t just an internal hiccup; it reflects poorly on DFINITY as a whole. How do we want to be perceived – as a cutting-edge protocol that values its history and community, or one that lets iconic assets decay due to inaction? Abandoning a blue-chip collection like Mechs sends the wrong message to builders, holders, and potential newcomers. We’ve seen similar issues with Sentinels and backdoor concerns in Ghosts – it’s time to resolve this pattern decisively.

I urge DFINITY leadership @dominic @JanCamenisch, @PierreSamaties, and the core team) to intervene immediately: enforce the agreed-upon transfer of the Mechs canister to the Motoko DAO, top up the cycles to restore functionality, and ensure the DAO can maintain and innovate on these assets as intended. Bob Bodily must fulfill his obligations now no more delays.

Let’s get this fixed and show the world what DFINITY stands for: decentralization, accountability, and respect for our shared achievements. I’d appreciate any support, insights, or actions from the community and team.

For reference, see my original X post calling attention to this: X Post on Mechs Abandonment.

Thank you for your attention let’s act before this becomes a bigger embarrassment.

Best,
dehypokriet (Dexter ∞ Caffeine/Acc)

2 Likes

@lara can you look into why this is getting censored ?

In a permission-less world, no one has to give you permission to keep something important to you running. If the canister is frozen and important to you, top it up: https://www.icptopup.com

Is motoko and “IP” owned by anyone? It is a language, it is an anime character, it is toon bot NFTs. If anyone has actually said/declared/filed a copyright it would be interesting to know. At this point I had just kind of considered it community property.:man_shrugging:

And while they are at it tell him to fix his Bioniq crap as well, can’t even login there anymore…

Toko market can’t come soon enough so we can wash away this sour taste some of these “Devs” have created…

Bob’s not going to do anything that doesn’t benefit him directly. Actions speak louder then words and all he’s done is ignore the community, endlessly pivot, abandon projects and enrich himself.

Either the foundation can pressure him into giving us control, or we’ll just fork the collection and mint it fresh on Toko.

1 Like

“In a permission-less world, no one has to give you permission to keep something important to you running. If the canister is frozen and important to you, top it up:”

  1. This issue arises because the people that own the controls to the canisters and benefit from it by royalties have abandoned it, so instead of ensuring those royalties go to the cycles they expect people like me who have paid 200 ICP to own some of those, to also keep them running?

its indeed a permssion-less world, but something representing a significant event, should be honored and maintained, not being written of as “community should take care of it”, you like to community to take care of it, fine but set all the royalty’s toward a account / adress that just tops up the cycles if its a “ community owned”

If its community property, the community should be the one profiting from it right?

Kyle did message me last night and added the cycles, so its running now, but again if you like to claim its “community owned, community property, ditch the royalties put it in one adress that just collects them and send them to cycle power the collection automatically, blackhole the cansiter, thats community owned

1 Like

My answers getting insta blocked not sure why but i have responded to you