-
Notifications
You must be signed in to change notification settings - Fork 75
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
docs: technical roadmap #219
base: docs-sprint
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nits. Good stuff @matt-user
|
||
## Testnet Roadmap | ||
|
||
#### New abi encoding scheme |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#### New abi encoding scheme | |
#### New ABI encoding scheme |
|
||
#### New abi encoding scheme | ||
|
||
The new abi encoding scheme will enable support for nested heap types. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new abi encoding scheme will enable support for nested heap types. | |
The new ABI encoding scheme enables support for nested heap types. |
#### New abi encoding scheme | ||
|
||
The new abi encoding scheme will enable support for nested heap types. | ||
This enables developers to return arbitrarily nested heap types from contracts and scripts, and log any arbitrary data type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This enables developers to return arbitrarily nested heap types from contracts and scripts, and log any arbitrary data type. | |
This enables developers to return nested heap types from contracts, scripts, and log any arbitrary data type. |
A data type allocated on the heap can grow or shrink in size. | ||
Compared to the built-in array and tuple types which are allocated on the stack and cannot grow in serialize. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A data type allocated on the heap can grow or shrink in size. | |
Compared to the built-in array and tuple types which are allocated on the stack and cannot grow in serialize. | |
A data type allocated on the heap can change in size, unlike built-in array and tuple types, which are allocated on the stack and remain fixed in size. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reads much better and "cannot grow in serialize." doesn't make sense
|
||
#### Forkless upgrades in Fuel Core | ||
|
||
Supporting forkless upgrades to the fuel core will allow changing logic on the fly for all nodes in the network. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain how forkless upgrades work in 1 or 2 setences?
#### Fuel wallet connectors | ||
|
||
Fuel wallet connectors enable users to sign transactions on the Fuel network using wallets such as Metamask or Phantom. | ||
These wallets are able to be used on Fuel through the use of predicates. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is enabled through Fuel's support for multiple signatures can you talk briefly about which ones we support? Like sha256, keccak256, etc
Doc page for Fuel's technical roadmap.