Summary
The contract deliberately has no on-chain list of jars. Discovery is
event-driven: create_jar emits jar_crtd, and indexers are expected to
reconstruct the jar list by scanning those events. The SDK only fetches tip
events, so it offers no way to do the thing the contract's design assumes.
Anything wanting to enumerate jars has to build its own filter and decoder,
which is exactly the encoding work this package already solved once for tips.
Acceptance criteria
Getting started
Fork this repository, clone your fork, and add this repo as upstream:
git clone https://github.com/<your-username>/novatip-sdk.git
cd novatip-sdk
git remote add upstream https://github.com/Novatip/novatip-sdk.git
npm install
Create a branch for this issue:
git checkout -b feat/fetch-jar-created-events
Suggested commit message:
feat: fetch and decode jar_crtd events
Run npm run lint, npm run typecheck, and npm run build before pushing, then open a pull request from your fork against main and link this issue. See the contributing guide for the full workflow.
Summary
The contract deliberately has no on-chain list of jars. Discovery is
event-driven:
create_jaremitsjar_crtd, and indexers are expected toreconstruct the jar list by scanning those events. The SDK only fetches
tipevents, so it offers no way to do the thing the contract's design assumes.
Anything wanting to enumerate jars has to build its own filter and decoder,
which is exactly the encoding work this package already solved once for tips.
Acceptance criteria
jar_crtdevents into a typed resultcarrying the jar id, owner, ledger and transaction hash.
the XDR encoding.
Getting started
Fork this repository, clone your fork, and add this repo as
upstream:Create a branch for this issue:
Suggested commit message:
Run
npm run lint,npm run typecheck, andnpm run buildbefore pushing, then open a pull request from your fork againstmainand link this issue. See the contributing guide for the full workflow.