Let's solve these crucial protocol weaknesses

[Manu]

Lots of great discussion here on many topics here! I’ll quickly reply wrt instructions limit:

@Zane

What if a new subnet type were introduced where, instead of having constrained execution rounds, each canister can run as long as it needs to (maybe with some loose safeguards to prevent infinite loops)?
In order to make this happen the “subnet” shouldn’t attempt to certify its entire state at a fixed interval but instead:

• Do the usual gossiping and ordering of messages
• Induct messages into canister queues
• Exhaust the canister queue at its latest certified height + 1
• Sign the canister state
• Gossip finalization shares on a per canister basis
• Certify canister state at latest height with enough shares

I don’t think you can certify things per canister, this might work for 10 canisters on a subnet but seems entirely unfeasible for 100k canisters on a subnet, because creating threshold signatures with all subnet nodes is still significant work.

@lastmjs

Instruction limits: there should be no limit as long as it is paid for

I agree this would be great. Currently I don’t think we know how we could extend DTS to go over checkpoint boundaries, so that’s one limitation we have now. We are planning to propose to double the DTS instructions limit (from 20B to 40B), so that should already help here. Increasing beyond that would likely be more involved, so I am not aware of any concrete plans there.