Contract File Format

The binary sent in a transaction should comply with the Rusk binary format, and should contain the following as payload:

In the transaction used to deploy a contract, the following needs to be included:

• Constructor arguments
• Owner information
• Bytecode

The bytecode should likely be compressed using a lossless compression algorithm such as zstd.

A contract should be deployed using the following manifest:

{
    "name": "test",
    "authors": ["Dusk Network <[email protected]>"],
    "repository": "https://github.com/dusk-network/rusk",
}