Skip to content

docs: technical roadmap #219

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.

Sign up for GitHub

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

Draft
wants to merge 4 commits into
base: docs-sprint
Choose a base branch
from
Draft

docs: technical roadmap #219

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5158170
docs: init technical roadmap
matt-user Apr 3, 2024
2363285
docs: technical roadmap info
matt-user Apr 4, 2024
1a61c94
docs: remove couple of sentences
matt-user Apr 4, 2024
0e60f3e
docs: add more info about roadmap
matt-user Apr 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ yarn-error.log*

# local env files
.env*.local
.env

# vercel
.vercel
Expand Down
5 changes: 2 additions & 3 deletions docs/fuel-101/nav.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
{
"menu": ["Transaction Model", "Transaction Lifecycle"]
}

"menu": ["Transaction Model", "Transaction Lifecycle", "Technical Roadmap"]
}
39 changes: 39 additions & 0 deletions docs/fuel-101/technical-roadmap.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
---
title: Technical Roadmap
category: Fuel 101
---

# Technical Roadmap

## Testnet Roadmap

#### New abi encoding scheme
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### New abi encoding scheme
#### New ABI encoding scheme


The new abi encoding scheme will enable support for nested heap types.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

This enables developers to return arbitrarily nested heap types from contracts and scripts, and log any arbitrary data type.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

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.
Comment on lines +14 to +15
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

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.
Copy link
Contributor

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?

This minimizes the impact to the network when upgrades take place.

#### SRC-20 standardization for bridged assets

#### 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.
Copy link
Contributor

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


#### The Graph integration

Integrating Fuel with The Graph allows developers to easily index and query blockchain data for their Dapps.
This integration will allow developers and users to easily aggregate, search, and filter the state of Dapps and the Fuel network.

## Post-Testnet Roadmap

#### Forced transaction inclusion

Forced transaction inclusion allows users to include transactions on Fuel even in the event of a sequencer failure.
This is achieved by sending the transactions to the L1 which includes the transaction in Fuel's block history.