Skip to content

docs: document forwarded RGB issuance methods on the account#23

Draft
Zhekinmaksim wants to merge 1 commit into
UTEXO-Protocol:mainfrom
Zhekinmaksim:docs/document-forwarded-rgb-issuance
Draft

docs: document forwarded RGB issuance methods on the account#23
Zhekinmaksim wants to merge 1 commit into
UTEXO-Protocol:mainfrom
Zhekinmaksim:docs/document-forwarded-rgb-issuance

Conversation

@Zhekinmaksim

Copy link
Copy Markdown

Follow-up to #22.

The README says RGB issuance "is not part of this module's API," but WalletAccountRgbLightning forwards issueAssetNia / issueAssetUda / issueAssetCfa / issueAssetIfa and inflate straight to the binding (src/wallet-account-rgb-lightning.js L667-L670, L705), under a section comment labelled RGB asset issuance + transfers — ✅ wired.

This is the documentation resolution from that issue — the smaller of the two options. It makes the README describe the surface that actually exists:

  • adds a RGB issuance (forwarded) row to the Account API table
  • rewords the two "not part of this module" lines so they say the calls are forwarded, while still pointing issuance-centric flows at @utexo/wdk-wallet-rgb

Docs-only, no behaviour change. If you'd rather go the other way — drop or deprecate the forwarders so issuance lives only in wdk-wallet-rgb — I'm happy to swap this for that diff instead.

The README states RGB issuance 'is not part of this module's API', but
WalletAccountRgbLightning forwards issueAssetNia/Uda/Cfa/Ifa and inflate
straight to the binding (src/wallet-account-rgb-lightning.js L667-L670,
L705), under a section comment labelled 'RGB asset issuance + transfers
- wired'. That left the documented surface and the actual surface out of
sync.

This is a docs-only change that makes the README match the code:
- add a 'RGB issuance (forwarded)' row to the Account API table
- reword the two 'not part of this module' lines to say the calls are
  forwarded here, while keeping @utexo/wdk-wallet-rgb as the recommended
  issuance path

No code changes; behaviour is unchanged.
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.

1 participant