Draft
Conversation
Contributor
calldelegation
left a comment
calldelegation
left a comment
There was a problem hiding this comment.
Small nits. Good stuff @matt-user
|
|
||
| ## Testnet Roadmap | ||
|
|
||
| #### New abi encoding scheme |
Contributor
There was a problem hiding this comment.
Suggested change
| #### New abi encoding scheme | |
| #### New ABI encoding scheme |
|
|
||
| #### New abi encoding scheme | ||
|
|
||
| The new abi encoding scheme will enable support for nested heap types. |
Contributor
There was a problem hiding this comment.
Suggested change
| 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. |
Contributor
There was a problem hiding this comment.
Suggested change
| 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. |
Comment on lines
+14
to
+15
| 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. |
Contributor
There was a problem hiding this comment.
Suggested change
| 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. |
Contributor
There was a problem hiding this comment.
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. |
Contributor
There was a problem hiding this comment.
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. |
Contributor
There was a problem hiding this comment.
This is enabled through Fuel's support for multiple signatures can you talk briefly about which ones we support? Like sha256, keccak256, etc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doc page for Fuel's technical roadmap.