Closed Latrasis closed 4 years ago
A placeholder clist is now being stored in AccountDb
successfully. Next step is to make that into a useful data structure.
I'm currently using an array of 7 booleans to represent the capabilities. As this data structure is not a critical part of the design I suggest we leave it as that for now while we focus on other things.
Something like DELEGATECALL
from Ethereum has been implemented which should take us toward completing this issue. Two important notes:
Closing this for now, considering we're dealing with an api that might not fit with what we expect.
Based on #198, we need to setup an srml runtime api including:
cap9_proc_call(proc_id: &str, input: &[u8], result: &mut [u8])
-> Result<Veccap9_proc_reg(proc_id: &str, addr: Option<Address>, cap_list: CapList) -> Result<(), Error>
cap9_proc_set_entry(proc_id: &str) -> Result<(), Error>
cap9_kernel_init(amount:U256, entry_code: &[u8])
.