FuelLabs/fuels-ts

Documentation for `B256`

Open

#3240 opened on Oct 2, 2024

View on GitHub
 (5 comments) (0 reactions) (0 assignees)TypeScript (43,186 stars) (1,370 forks)batch import
docsgood first issue

Description

Summary

Reference docs

  • We could rename these to B256 from Bits256to better align with the wider ecosystem.
  • Currently we display how use getRandomB256 however I believe we should use actual addresses for a better showcase of their use cases.
  • We're missing how to use these addresses with an actual contract.
  • We're also missing how these can be used in Sway programs.

Contributor guide

Tech stack
typescript
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of Fuel SDKFamiliarity with Sway programs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Review the current documentation at https://docs.fuel.network/docs/fuels ts/types/bits256/. Examine the implementation of B256 in the SDK source code. Look for existing examples of address usage and contract interactions. Consider addressing comments in the issue for further clarification.