We have received quite a bit of feedback from the community about our lack of public communication.
This stems from having a million things to do and never having enough time to do it, as well as us not making public communication a priority.
Well, we're going to do better. So ask away. Questions? Concerns? Feedback?
An update was made to the Internet Computer Protocol a few weeks ago which made a few older collections (like OG Medals) burn a large amount of cycles.
So we stopped the canisters and we're working through them to make them more efficient (burn fewer cycles) to get them back online.
You can find reproducible build instructions in the Motoko Ghosts folder Readme.
(note you may have to use dfxvm to switch dfx versions between canisters, see the dfx.json within each project for the correct dfx version to use)
Here's a link to the repo: https://t.co/S66YqJE1pf
Reproducible build update!
We now have reproducible builds available for:
- Motoko Ghosts
- Pet Bots
- The Pixel Collection (Jon Ball)
- Poked Bots Mutant Army
- Poked Bots (coming soon)
This means anyone can independently verify the canister code for these collections.
We had to change our marketplace stats backend architecture because making hundreds of calls at the same time to fetch canister data was giving people a 10 minute soft-ban by ICP boundary nodes (all ICP calls across the entire network would subsequently fail for a 10 minute period).
The collection is still there if you search for it, the stats just must not be populating correctly post our update mentioned above. We'll need to fix.
Dfinity Space Apes canister is now back online!
We'll be monitoring cycles usage over the next few weeks to ensure it is working efficiently with minimal cycle burn.
We shouldn't have this problem in the Poked Bots Mutant Army collection anymore. If you are seeing issues, please report them and we'll take a look.
We're working on a reproducible build process for this canister so that anyone can verify the code that wants to.
@pokedstudiouk@DJG24_7@BobBodily There have been some intermittent issues with heartbeats and timers (aka cron jobs) on ICP over the last few weeks, and the process keeping the Pet Bots canister going had stopped.
So we added some of our latest timer / monitoring methods and redeployed to fix the issues.
We are working on increasing transparency for NFT canister code, and we will be rolling this out to other canisters over time (public Github repo with code, reproducible build process, etc).
Great news everyone!
We now have a reproducible build process for the Motoko Ghost NFT canister.
It isn't perfect (requires Linux/Ubuntu), isn't packaged in Docker yet (likely best way for the future), but it works!
Now anyone can independently verify the code themselves.
If you attempt to replicate the canister .wasm binary let us know how it goes!
And if you get a different WASM binary hash (the SHA256 hash of the .wasm file) we're happy to help debug.
(for example, we're still unsure whether all versions of Linux/Ubuntu work)
We have received quite a bit of feedback from the community about our lack of public communication.
This stems from having a million things to do and never having enough time to do it, as well as us not making public communication a priority.
Well, we're going to do better. So ask away. Questions? Concerns? Feedback?
What kind of transparency are you looking for? Here are some options:
- Canister upgrades
- $$ spent on topping up cycles
- Time spent helping users with bugs
- Time spent fixing canister issues
- Canister code
- Canister controllers
- Other tooling used to maintain canisters
- Asset canister maintenance
- NFT canister technical architecture paradigms
- Current limitations of NFT canisters
- Best NFT setup for the future of ICP
What are the current community thoughts on the $BOB token on ICP?
Is cycles burning to earn a token the future of ICP?
Does $BOB need to add utility to make it sustainable?
When the halving hits mining becomes unprofitable. Will people still mine?