Some wedding photographer has acquired the domain and is hosting their wedding photography page on it. WHAT WE BUILT IS NOT WHAT IS HOSTED THERE
Is that not apparent there? It’s a wedding photographer’s portfolio website. NOT WHAT WE BUILT.
We’re not. This thread is focused on Yral updates. We are going to limit responses to Yral here.
If I had to take a stab, I imagine it’s because reusable UI components would have been borrowed between the apps. The 2 apps:
were built by the bootstrapped team with no grant funding with a single dev that we’ve helped recruit and mentor.
Since there’re commonalities between the ICRC 7 NFT minter for EstateDAO and FuelEV, I imagine some code would be shared.
There was a significant amount of overlap in this code the first time Fuel EV had tried to go through the SNS. They were rejected basis that and they took that feedback to heart, persisted for approx. 6 months and obtained approval from the NNS DAO to participate.
Hey Adam 
Sending cycles back and forth would simply be update calls between canisters. Canisters would pay for the cycle cost associated with intercanister calls. The network wouldn’t be overwhelmed with update calls between canisters on a subnet.
I’m not sure who reviewed the code on your behalf but as far as I can remember you asked for links to our canister code and you reviewed the entire bit in detail including verifying the WASM hashes to match what we’ve deployed is what the code provided is.
The problematic bit of code that you showed was querying cycle balances of children canisters from parent canisters and sending cycles from the parent canister to the children canister and was doing it in a batch of 10 and not individually 1 by 1. It’s an optimization so that canister topups can happen as fast as possible. I imagine OpenChat does the same.
If you have a fleet of canisters, you would parallelise. Nothing wrong with that
You wouldn’t actually. You are assuming query calls, which have only recently been enabled for intra subnet calls, inter subnet query calls don’t work yet
So that wouldn’t work. So you would do update calls here and we know what latencies for that look like. It would be a painfully slow call.
And this is just the top level orchestrator obtaining the balance from the subnet orchestrator. The subnet orchestrator also needs to do this for all individuals it controls.
But Mimic is pretty cool
Yep, I remember. I probably have another an additional year of experience 
We did vibe on a bunch of Rust code for so long. You used to like my function names 