Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the ABI spec with the new JSON ABI format #416

Merged
merged 11 commits into from
Oct 20, 2022
Prev Previous commit
Lint
mohammadfawaz committed Oct 14, 2022
commit 972273674a504cb9712192457c57b01ee7da6125
2 changes: 0 additions & 2 deletions specs/protocol/abi.md
Original file line number Diff line number Diff line change
@@ -61,8 +61,6 @@ The ABI of a contract is represented as a JSON object containing the following p
- `"type"`: the _type declaration_ ID of the type of the _type argument_.
- `"typeArguments"`: an array of the _type arguments_ used when applying the type of the _type argument_, if the type is generic, and `null` otherwise. The format of the elements of this array recursively follows the rules described in this section.

> **Note**: The order of entries in `"inputs"`, `"outputs"`, `"components"`, `"typeArguments"`, and `"typeParameters"` is important and should be taken into account when encoding/decoding an ABI.

> **Note**: This JSON should be both human-readable and parsable by the tooling around the FuelVM and the Sway programming language. There is a detailed specification for the binary encoding backing this readable descriptor. The [Function Selector Encoding](#function-selector-encoding) section specifies the encoding for the function being selected to be executed and each of the argument types.

### A Simple Example