Skip to content

BRC-175: 1Sat Fungible Basket Profile - #237

Draft
GenericCPU wants to merge 5 commits into
bsv-blockchain:masterfrom
GenericCPU:docs/brc-166-onesat-fungibles
Draft

BRC-175: 1Sat Fungible Basket Profile#237
GenericCPU wants to merge 5 commits into
bsv-blockchain:masterfrom
GenericCPU:docs/brc-166-onesat-fungibles

Conversation

@GenericCPU

@GenericCPU GenericCPU commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds BRC-175: fungible 1Sat tokens as 1-sat tips sharing one origin, each with face-value amt (balance = Σ amt).

  • Storage basket 1sat-ft (separate from NFT 1sat)
  • Transfers spend tips and create payee (+ change) 1-sat tips with conserved amt; imports BRC-150 provenance
  • Locked supply optional (supply + max on origin); omit when uncapped
  • Mint-batch attestation for same-tx genesis siblings; missing amt ⇒ 1 (legacy)
  • Chain scan / basket separation: bare 1-sat tip moves are shared with BRC-147; MUST NOT auto-file into 1sat on “spent a 1-sat parent” alone; FT lineage (application/1sat-ft+json) MUST NOT paint as NFT. Documents old-client misfile / burn risk. Cross-note added on BRC-147 Compatibility / Security.

Number: 175 (was briefly drafted as 166; 175 is free on upstream).

Implemented in HandCash wallet for hold/send/receive; mint via BRC-100 / Mint Studio.

Test plan

  • Spec review (David / 1Sat maintainers especially welcome on amt conservation + optional lock)
  • Confirm basket name 1sat-ft is acceptable
  • Confirm number 175 is still free at merge time
  • Review bare-transfer coexistence with BRC-147 ingest heuristics

GenericCPU and others added 3 commits August 27, 2026 14:06
Shared-origin fungible tips (1 tip = 1 unit), basket 1sat-ft, mint-batch
binding, open/locked supply; imports BRC-150 provenance format.

Co-authored-by: Cursor <cursoragent@cursor.com>
Replace tip-count v1 with amt + split/change conservation; locked supply is optional on the origin.

Co-authored-by: Cursor <cursoragent@cursor.com>
0166 was provisional; 0175 is free on upstream. Same basket profile content.

Co-authored-by: Cursor <cursoragent@cursor.com>
@GenericCPU GenericCPU changed the title BRC-166: 1Sat Fungible Basket Profile BRC-175: 1Sat Fungible Basket Profile Aug 27, 2026
Readers and writers use 1sat-ft only.

Co-authored-by: Cursor <cursoragent@cursor.com>
@GenericCPU
GenericCPU marked this pull request as draft August 27, 2026 20:31
@ty-everett

Copy link
Copy Markdown
Collaborator

Is this stuff using the BRC98/99 semantics like BTMS does, at the wallet layer?

Or is this operating above that and just reserving the basket name for the application layer?

Spell out that bare 1-sat tip moves are shared with collectables, so chain
scan must not auto-file them into basket 1sat, and FT lineage must not paint
as NFT. Documents old-client misfile / burn risk.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants