Follow-up from "Execution spec": Syscalls

[massa-bot]

In GitLab by @AureliaDolo

The following discussion from !374 should be addressed:

• @Adolo started a discussion: (+1 comment)

  Is this list exhaustive ?

TODO: list syscalls exhaustively

[massa-bot]

In GitLab by @damip

we need to think about it, but it is linked to the developer experience :) (what we want to expose to the SC devs)

[adrien-zinger]

Execution.md said:

Smart contract creation and interaction:

• Call(SC_addr, function_name, parameters): synchronously calls a function in the same, or another smart contract
• NewSC(balance, data, program) -> SC_addr : creates a new smart contract with initial balance, data and program. Returns its automatically generated address (SCE ledger) on success.
• TransferToConsensus(amount): transfers massa coins from SCE ledger to the consensus ledger. On the SCE side, this just burns the coins.

Smart contract context management:

• WriteDatabase(key, value): writes in the database of the current smart contract
• ReadDatabase(SC_addr, key): reads a value from an arbitrary database
• GetContext -> Context: returns the call context (block, stack, available coins, max_gas, etc...)

I suggest to add a self() ABI to split the GetContext that is really big.

[adrien-zinger]

I have heard of a GetTime that is missing here

[AureliaDolo]

What would get_time be ? Should it be slot related ?

[AureliaDolo]

@adrien-zinger is there a link between this call and this one :

Call(SC_addr, function_name, parameters): synchronously calls a function in the same, or another smart contract

[adrien-zinger]

Yes it's what we're speaking about. But the notion of blockclique, determinisme and time are defined in massa_execution. cautious bassoon asks massa for a data/bytecode/random etc... and just focus on the execution.

[AureliaDolo]

I didn't quite got it :/